Looks like my previous email only went to Ahmad... To add to my below response. I also installed bind9 on my management server and set it up as a caching dns to rule out issues with our corporate MS dns servers and still does not work.
On Tue, Apr 30, 2013 at 3:41 PM, Carlos Reategui <car...@reategui.com>wrote: > > On Tue, Apr 30, 2013 at 3:18 PM, Ahmad Emneina <aemne...@gmail.com> wrote: > >> looks like you cant route out to the internet. can you ping 8.8.8.8 >> directly from the ssvm? >> > > Network connectivity appears fine. As you can see from the test script it > is able to ping the internal DNS server. I am also able to ping Google's > DNS: > > root@s-1-VM:~# ping 8.8.8.8 > PING 8.8.8.8 (8.8.8.8): 56 data bytes > 64 bytes from 8.8.8.8: icmp_seq=0 ttl=45 time=30.694 ms > 64 bytes from 8.8.8.8: icmp_seq=1 ttl=45 time=23.546 ms > > However I just recalled our corporate network does not allow external dns > so I need to stick to the internal one that the SSVM is already configured > for. > > The odd thing is if I try to telnet to port 53 it says no route to host > (Is there a similar way to test a udp connection?): > root@s-1-VM:~# telnet 172.30.20.176 53 > Trying 172.30.20.176... > telnet: Unable to connect to remote host: No route to host > > But yet a ping works. > > root@s-1-VM:~# ping 172.30.20.176 > PING 172.30.20.176 (172.30.20.176): 56 data bytes > 64 bytes from 172.30.20.176: icmp_seq=0 ttl=127 time=0.690 ms > 64 bytes from 172.30.20.176: icmp_seq=1 ttl=127 time=0.674 ms > 64 bytes from 172.30.20.176: icmp_seq=2 ttl=127 time=0.674 ms > > Traceroute looks ok: > root@s-1-VM:~# traceroute -n 172.30.20.176 > traceroute to 172.30.20.176 (172.30.20.176), 30 hops max, 60 byte packets > 1 172.30.45.32 0.273 ms !X 0.235 ms !X 0.211 ms !X > > any other ideas? > > > > > >
