Comment by apps@enoges.com :

ohh Yeahh!!!
Yes!! Everything is ok now!!!
Thanks a lot Henar…
Could I know which was the issue??

> El 19 may 2016, a las 15:27, Help-Desk <jira-help-desk@fi-ware.org> escribió:
>
>
> Hi
> Ok. I understood. Please try it now, and tell me
> Regards,
> Henar
> <image3599485977676383295.png> FW External User <x-msg://10/secure/ViewProfile.jspa?name=fw.ext.user> created an issue
>
> Help-Desk <https://jira.fiware.org/browse/HELP> / <https://jira.fiware.org/browse/HELP-6601> HELP-6601 <https://jira.fiware.org/browse/HELP-6601>
> [Fiware-lab-help] Unavailable Server <https://jira.fiware.org/browse/HELP-6601>
> Issue Type: extRequest
> Assignee: Henar Muñoz <x-msg://10/secure/ViewProfile.jspa?name=henar>
> Components: FIWARE-LAB-HELP
> Created: 16/May/16 11:47 AM
> Priority: Major
> Reporter: FW External User <x-msg://10/secure/ViewProfile.jspa?name=fw.ext.user>
> Hi.
> We had several instances on Fiware Cloud. We have a “proxy” instance with iptables that makes routing to other machines. How ever, I can’t access to my virtual machines from “proxy”. Hosts are unreachable, but in Fiware cloud portal these instances are running.
> Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
> Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
>

Comment by apps@enoges.com :

Hi again Henar.

I couldn’t be, we have been always connecting from ProxyVM to the other instances. Why the other instances are now in a different network???

> El 19 may 2016, a las 11:30, Help-Desk <jira-help-desk@fi-ware.org> escribió:
>
>
>

The issue has been emailed:

• Time sent: 19/May/16 11:29 AM
• To: apps@enoges.com
• with subject: *(HELP-6601) [Fiware-lab-help] Unavailable Server *
  

Hi again
It seems you are trying to access from ProxyVM, which is in a different network that the other VM, so that, they are not accesible.
Regards,
Henar

011b2fb1-7001-4d3a-8b13-8fe540da2b17 | ProxyVM | 00000000000000000000000000006550 | ACTIVE | - | Running | n1=192.168.192.24, 130.206.116.94

The issue has been emailed:

• Time sent: 19/May/16 11:28 AM
• To: apps@enoges.com
• with subject: *(HELP-6601) [Fiware-lab-help] Unavailable Server *
  

Hi
From the DHCP in that network I can access to the VM:
ssh root@192.168.192.26 -p 2221
root@192.168.192.26's password:

When you are trying to access?
Henar

Comment by apps@enoges.com :

By the way. I have installed nbtscan in order to know computers close to my network, and also get cache arp. I have done the following steps:
1. ping to broadcast interface.
2. arp -a . In this step I get an incomplete mac for server, and a computer with ip 192.168.192.29 that is not mine (i think)
root@proxyvm:/home# arp -a
? (192.168.192.26) at <incomplete> on eth0
? (192.168.192.21) at <incomplete> on eth0
? (192.168.192.29) at fa:16:3e:94:fd:f8 [ether] on eth0
? (192.168.192.1) at fa:16:3e:85:50:3c [ether] on eth0

3. Unable to get computers in my net with nbtscan in range 192.168.192.24-29

root@proxyvm:/home# nbtscan 192.168.192.24-29
Doing NBT name scan for addresses from 192.168.192.24-29

IP address NetBIOS Name Server User MAC address
------------------------------------------------------------------------------
root@proxyvm:/home#

Thats all. Maybe this information can help you

Thanks again!!

> El 19 may 2016, a las 10:34, Javier Garrido Díaz <apps@enoges.com> escribió:
>
> Hi Henar.
> No, the problem is still there. I sent you a screenshot. When I try to connect to server, i get the message “No route to host”. I paste you the screen:
>
> root@proxyvm:/home# ssh -i SmartTillageKeypair.pem root@192.168.192.26 <root@192.168.192.26> -p 2221
> ssh: connect to host 192.168.192.26 port 2221: No route to host
>
> Thanks!!
>
>
>> El 19 may 2016, a las 10:23, Help-Desk <jira-help-desk@fi-ware.org <jira-help-desk@fi-ware.org>> escribió:
>>
>>
>>
>