Sign in with
Sign up | Sign in
Your question

Can't ping or visit select sites

Last response: in Networking
Share
February 24, 2010 3:59:27 PM

Hello,

Something very strange has happened with in our company since last night. We had a client application put on one of our server to update our database to theirs. It seemed to communicate fine with the external server and now..

1. Doesn't ping ONLY from the server we want to receive the update. (My PC pings fine)
2. Also I discovered, some other sites won't ping or open in a browser all of a sudden! Google being the biggest name I can think of! Pings and browser access fail. Yahoo for instance, does load.

I am posting my ipconfig /all up to let me know if you notice anything. On a tracert it hits our firewall 192.168.1.1 then all fail there after. Please if anyone knows why this was caused and how to change it I would appreciate it.
*Windows Server 2008 standard R2 edition.
*Checkpoint Firewall
(ipconfig /all)
Windows IP Configuration

Host Name . . . . . . . . . . . . : Apollo
Primary Dns Suffix . . . . . . . : aegis.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : aegis.com

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Local Area Connection - Virtual Network
Physical Address. . . . . . . . . : 00-26-55-1A-45-04
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::D 865:f860:8251:4ed5%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.234(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.235(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.236(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.237(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.238(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.239(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.240(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.241(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 335554133
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-B6-94-5B-00-26-55-1A-45-04
DNS Servers . . . . . . . . . . . : 192.168.1.2
192.168.1.3
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{A6D2B22A-D7C1-4BA8-934C-A51F582D617B}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
February 24, 2010 5:15:48 PM

Appears to me you're using IPv6, any reason you're not using IPv4?
m
0
l
February 24, 2010 6:05:54 PM

If you are not using IPv6, Turn it off as I have seen this cause problems.
I would look through the firewall settings for servers ip addresses. I am assuming that in order for the company to connect you had to forward some ports. Check and make sure something else did or didn't get configured.
m
0
l
Related resources
February 26, 2010 2:04:35 PM

Nope, very good observation on the IPv6 though. I saw it and it didn't even cross my mind. We have no use for it and I shut it off (excited of course). Google pinged, I almost wet my pants, then 5 minutes later, google wouldn't ping. I really don't understand this. Between amazon, ebay, and google, they ping when they want, then they won't. This includes our database source - it has the same behavior.

Taking a closer look at the firewall now, but I have yet to pull anything solid from that either.
m
0
l
February 26, 2010 2:14:57 PM

IP Tools
Ping cornerstone.mris.com - Please wait...
PING 65.222.239.173 (65.222.239.173): 56 data bytes
64 bytes from 65.222.239.173: icmp_seq=0 ttl=54 time=465.5 ms
64 bytes from 65.222.239.173: icmp_seq=1 ttl=54 time=1378.3 ms
64 bytes from 65.222.239.173: icmp_seq=2 ttl=54 time=599.4 ms
64 bytes from 65.222.239.173: icmp_seq=3 ttl=54 time=188.5 ms
64 bytes from 65.222.239.173: icmp_seq=4 ttl=54 time=118.7 ms

--- 65.222.239.173 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 118.7/550.0/1378.3 ms


I wanted to add this. I just sent this to our database server we are attempting to connect and this was from our actual firewall device. It has to be a problem on the server. Its running Windows Server 2008 R2, we have virtual IP's set up. I don't believe (I say believe because I never used google, or amazon, etc before this database problem so maybe its been going on!) the problem ever occured before we installed the client to connect to the database. You can even check it out for yourself at http://www.mris.com/ it seems like such a basic program, that I don't see how it could cause a confusion such as this.
m
0
l
!