Network Problem - Connection Loss

April 22, 2011 at 13:42:56
Specs: XP Pro SP3, Pentium 4 / 1GB
I am experiencing a problem with a few computers that loss internet connection loss intermittently throughout the day. There are no issues with LAN connection.
I have read similar postings with the same issue but haven't found a solution.
The network is 1 domain/1 subnet/ 10 computers (4 are having the internet problem), Server SBS 2008 (DHCP).
If I ping the gateway I never get a request time out, however if I ping a website after 5 minutes, I get a request timeout. I ping via IP address as well to website to see if there is a DNS problem but I get the same result, good connection and then request timeout after 5 minutes.

Here is what I have done so far to try to identify the problem:
-I plugged one of the computers that are having the internet problem directly into the ISP router (using static IP) and the internet connection never drops/no request timeouts.
- I turned off the antivirus/firewall on the computers that are having a problem
- I did a reset of TCP/IP / Winsock on the NIC cards.
- Some of the computers on the LAN do not lose internet connection at all. I moved a one of the computers that is having a problem over to use the same network cable connection on a computer that is not having a problem.
- The only way I can get the internet connection back is wait for 30 minutes or also if I go into the Network Card Properties advanced tab and then click ok, the internet connection comes back immediately.
- I changed the NIC speed/duplex properties from AUTO to 100M/Full Duplex and Flow Control on. I still get request timeout but I notice the computer stays online a little longer, (15 minutes as opposed to 5 min when set to AUTO). I did a reset on the default gateway router/upgraded the firmware. I upgraded the drivers on the NIC cards. But the problem is still occurring. Any ideas on what else to try? I am hesitant to replace the NIC cards (a few are laptops and the office is remote to my location). Also apparently the office recently replaced the router gateway and the issue appears to have gotten worse, not sure if there is a setting on the router that is being missed (but it isn’t impacting all computers).


See More: Network Problem - Connection Loss

Report •


#1
April 22, 2011 at 16:04:54
What router do you have? Have you tried using the router as your DHCP server?

Internet > modem > router > switches > all PCs including the server.

That should be your network topology.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
April 22, 2011 at 18:51:11
Thanks for the info.
Yes that is how the network topology is setup.
The server is setup to handle the DHCP (although there may be an issue on configuration. The router is a Netgear WNR 3500L. It was originally set for DHCP but after discovering the issue I removed DHCP (since it was setup on the server) but the problem is still occurring.
However not all computers are having an issue getting request time to the internet (it is 1 domain/1 subnet setup).

Report •

#3
April 22, 2011 at 19:13:49
Does the server have a static internal IP address? It should. Actually, since there are only 10 PCs, you can use static IPs for all of them.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
April 22, 2011 at 21:15:45
Yes, the server has a static IP. I also set a static IP on a couple of the computers that are having a problem with internet connection as well but it didn't fix the issue.

Report •

#5
April 23, 2011 at 05:56:32
Look at the event viewer on the problem PCs.

How do you know when a politician is lying? His mouth is moving.


Report •

#6
April 23, 2011 at 09:57:49
I see a couple Event ID's - (Application): 1054 and 1085 and (System): 11191
I will investigate further what they mean/cause. Note: these ID's are not being generated at the time I start getting the Request time out so I am not sure if they are related.
Also, I installed Network Monitor and filtered on DNS and also Generic Networking Events, I can see where the ICMP Echo Request/Reply occurring and then eventually after 5 minutes there is no longer a Echo Reply. In reading the CAP file I don't see anything yet that would cause the Request time out. It's very strange that when I refresh the network card properties it starts to work again (but I don't need to do this when I PING anything on the LAN, including the default gateway -I never get Request Time out for a local ping).

Report •

#7
April 23, 2011 at 10:33:00
http://eventid.net/display.asp?even...

eventid.net can be searched for those events. Did you see those errors on the server itself or on the workstations? Look at both.

How do you know when a politician is lying? His mouth is moving.


Report •

#8
April 23, 2011 at 12:48:00
For System Event ID: 11191 I found a comment related to a DNS issue.
I ran the recommended commands:
ipconfig /flushdns, ipconfig /displaydns, and ipconfig /registerdns
after waiting 15 minutes I ran ipconfig /displaydns again.
I also did this on a workstation computer that is not having the problem with request time outs. On the computer that is working ok when I do the ipconfig /display dns I get back a string of websites (about 20) along with the record name, type, TTL, data length,record, section, A (Host Record) ....127.0.0.1 and No records of Type AAAA

- When I run the ipconfig /displaydns on the computer that is having the problem, I don't see any websites listed and here is what I get back instead:

C:\>ipconfig /displaydns
Windows IP Configuration
1.0.0.127.in-addr.arpa
----------------------------------------
Record Name . . . . . : 1.0.0.127.in-addr.arpa.
Record Type . . . . . : 12
Time To Live . . . . : 477873
Data Length . . . . . : 4
Section . . . . . . . : Answer
PTR Record . . . . . : localhost

domainsrv *note: domainserv is the hostname of the PDC Server on the LAN
----------------------------------------
Name does not exist.
brn_97ef56
----------------------------------------
Name does not exist.
brne561a9
----------------------------------------
Name does not exist.


localhost
----------------------------------------
Record Name . . . . . : localhost
Record Type . . . . . : 1
Time To Live . . . . : 477873
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 127.0.0.1


Report •

#9
April 23, 2011 at 15:33:05
http://support.microsoft.com/kb/959085

Take a look at that page. It mentions a hot fix that you might need.

How do you know when a politician is lying? His mouth is moving.


Report •

#10
April 23, 2011 at 19:13:13
Thanks for the link. I think that applies to the other computer that is working correctly (there are a lot of entries in the host file for blocking rogue websites).
I also did another test: PATHPING.
When I do a PATHPING to Google.com from both a good and bad computer both complete the trace, but the bad machine has an extra entry in the results, it shows the PATHPING coming back to the computers hostname/address 0.0.0.0. Not sure what this means.
I pasted the results of the PATHPING for the bad computer below.
*Note: Line Number 7 does not show up in the PATHPING for the good computer
but both PINGs complete (I masked the full static ip address xx and domain name):
>PATHPING google.com
Tracing route to google.com [74.125.93.106] over a maximum of 30 hops:
0 hostname.domainname.local [192.168.0.14]
1 * 192.168.0.1
2 ool-4b6384a9.static.ISPAddress.net [xx.99.132.xx]
3 * * *
Computing statistics for 4294966 seconds...
Source to Here This Node/Link
4. hostname.domainname.local [192.168.0.14]
5. 192.168.0.1 0/ 100 = 0% |
6. ool-4b6384a9.static.ISP.net [xx.99.132.xx]
7. hostname.domainname.local [0.0.0.0]
Trace complete.


Report •

#11
April 23, 2011 at 20:34:10
0 hostname.domainname.local [192.168.0.14]

There ^^ DNS resolved the name. It had an IP address.

7. hostname.domainname.local [0.0.0.0]

There it did not. Had it dropped off the network by the time you ran pathping? If you run ipconfig /all on a problem machine at that point & the NIC shows 0.0.0.0 , then it's losing it's IP address, possibly due to the naming convention. Is there a DNS and Windows Computer Name Mismatch?

How do you know when a politician is lying? His mouth is moving.


Report •

#12
April 23, 2011 at 22:07:49
When the computer gets a request time out to the internet, I did an ip config and maintains an IP address. I never get request time out to the default gateway, only for an internet address (using either the IP Address or Domain Name of a website address). I am not sure what you mean by a DNS and Windows Computer Name Mismatch, can you please clarify. When I do an IPConfig /all, I see the correct hostname of the computer and all the Primary DNS Suffix. I compare this info to a computer that is working correctly and I don't see any differences in the settings.

Report •

#13
April 24, 2011 at 01:59:57
I don't think it is a DNS/Internet issue at this point.
When I do PING to the IP Address of the ISP router that is at the office, it displays a Request Timed Out after 5 minutes. However, if I PING the default gateway from the same computer, I never get a Request Time Out.

Report •

#14
April 24, 2011 at 06:33:10
0.0.0.0 tells me that something doesn't see the IP address. It could be something in Active Directory. I would at least go back to DHCP in the router. Make sure that both DHCP servers aren't running at that same time.

How do you know when a politician is lying? His mouth is moving.


Report •

#15
April 24, 2011 at 10:10:11
Ok. Just to clarify should I enable the default gateway router for DHCP again?
Do I need to disable something on the server? One thing to note, all the computers that are having an issue of getting disconnected from the Internet are XP Pro w/ SP3. The other computers are working ok are Vista and Windows 7.

Report •

#16
April 24, 2011 at 13:57:23
What do you mean by the "default gateway router"? Don't tell me that you have more than one router on the network?

How do you know when a politician is lying? His mouth is moving.


Report •

#17
April 24, 2011 at 19:51:28
The network setup is this:

ISP Cable Modem / Router * this I don't have access to
v
Default Gateway Router (Netgear)
v
Domain Server
v
10 Workstations


Report •

#18
April 25, 2011 at 06:17:58
What do you mean you don't have access? Who's network is it? If it's not yours, why haven't you asked the owner to fix the problem?

How do you know when a politician is lying? His mouth is moving.


Report •

#19
April 25, 2011 at 12:08:42
The problem isn't coming from the ISP router.
If you connect one of the computers having an issue directly into the ISP router (with Static IP/DNS) then there isn't a problem when PINGing. It only happens when connected to the LAN (default gatway/server) then there is an issue with the PINGing getting request time out. But again it only happens to certains computers, not all of them.

Report •

#20
April 25, 2011 at 14:21:32
I question the use of 2 routers if that's the setup.

How do you know when a politician is lying? His mouth is moving.


Report •

#21
April 25, 2011 at 17:01:00
The ISP provides a router with a Public IP address (static). The client does not have access to configure the router for the internal LAN address. The second router is owned by the client and that contains the internal address 192.168.0.x that does the routing for everything on LAN.

Report •

#22
April 25, 2011 at 19:55:36
I think that's the problem. Whomever has access has to be contacted. I can't see any other way.

I learned something from this thread, which is, I should ask for the network topology before I answer.


How do you know when a politician is lying? His mouth is moving.


Report •

#23
April 25, 2011 at 20:36:31
But here is the problem. It is not affecting all computers on the LAN.
Only some of the computers are getting the request timeout.
A tech fro the ISP was already at the site, He was able to connect to the web fine, so he left. They usually don't get involved with network related issues.

Report •

#24
April 26, 2011 at 05:31:39
I didn't say to contact the ISP. I said to contact the owner of that other router, if in fact it is a router. If it's a straight modem, then you are correct. At the very least, you need a make & model of it.

How do you know when a politician is lying? His mouth is moving.


Report •

#25
April 27, 2011 at 10:06:41
The ISP owns the router. When I plug a computer that is having a problem with internet connection loss directly into the switch port of the ISP Router and give it a static IP/DNS address then there are NO issues with internet connection loss. I don't think the issue is between the ISP router and the Default Gateway Router on the LAN.
I have read a lot of info on connectivity issues with XP computers and 2008 Server.
Apparently, the older NIC cards have some conflicts with some of the advanced properties settings in 2008 Server NIC settings (Offload, etc). I removed some of the features and it definately has improved connectivity (including with RDP). The Internet cnnection still drops after 5 minutes (only on XP workstations on the LAN)- I am still researching the cause. Thanks for all the feedback.

Report •

#26
April 27, 2011 at 11:46:21
I don't understand why you have a second router. I have Verizon FIOS. They supply a wireless router. There is no reason for me to put a second router on the network, when the supplied router can handle 253 computers. At the most, I have 6 running at the same time. Replace that second router with a switch & your problems will be over.

How do you know when a politician is lying? His mouth is moving.


Report •

#27
April 27, 2011 at 13:12:46
I am not familiar with Verizon FIOS routers and their setup.
I am not sure why having more than 1 router on the network would cause a problem?

Report •

#28
April 27, 2011 at 15:08:40
The biggest mistake with 2 routers is forgetting to shut DHCP on one of them. That's just for starters.

How do you know when a politician is lying? His mouth is moving.


Report •

#29
April 27, 2011 at 16:53:10
DHCP is not configured. I tested the ISP router and could only connect with the Static IP setup. I also shut off DHCP on the internal router.

Report •

#30
April 27, 2011 at 17:36:39
There is a conflict or incompatibility somewhere. You just have to find it.

How do you know when a politician is lying? His mouth is moving.


Report •

#31
April 27, 2011 at 18:27:34
I think it is with the DNS between XP and SBS 2008, the Vista and Windows 7 Computers on the LAN are not having an issue. I will let you know if i find anything.

Report •

#32
April 27, 2011 at 18:50:59
Ok, let me know what you find.

How do you know when a politician is lying? His mouth is moving.


Report •

#33
April 30, 2011 at 22:41:48
Guapo, I figured it out. There is a third device somewhere in the building that was conflicting with the default gateway router. The problem in figuring this out is that it is not online all the time. There was an ARP conflict, but it was only affecting XP computers. Once I changed the internal IP of the default gateway and updating the computers to static IP's, everything is working fine now. Thanks for the help.

Report •

#34
May 1, 2011 at 04:39:34
I'm glad to hear it's all working now.

How do you know when a politician is lying? His mouth is moving.


Report •

Ask Question