Windows Thread, Network Problem in XP in Technical; I've been experiencing a network problem with some XP machines which I have never seen before, seem to be a ...
-
9th July 2010, 10:53 AM #1 Network Problem in XP
I've been experiencing a network problem with some XP machines which I have never seen before, seem to be a pain to fix.
The computer looks, and seems to be connected to the network absolutely fine. It has the correct proxy information, it gains a valid IP address with the correct subnet mask and is using the correct gateway.
However, the computer can't connect to the internet or any internal servers. This includes mail servers and file servers.
The weird thing is, I CAN ping Google and I CAN ping all our servers by both name and IP Address.
A tracert to Google shows the predicted results.
We're using Dell Optiplex machines with many different generations and models, but it seems to affecting different models, not just one kind of model. All of the machines are running XP with SP3.
I've tried updating network drivers and updating the BIOS, both of which were unsuccessful. I released the IP address and renewed it, and flushed the DNS; again both unsuccessful in fixing the problem.
One PC was fixed by re-imaging it, so I'm convinced it's not a hardware problem and inside XP. It's happened to a couple, and if it keeps happening I don't want to end up re-imaging the whole school.
Has anyone encountered this before or able to help with any more troubleshooting tips?
-
-
IDG Tech News
-
9th July 2010, 11:33 AM #2
-
-
9th July 2010, 11:38 AM #3 I had this happen on a new server just this week while downloading and installing new updates. It fixed the issue itself after a restart so didn't look into it any further, sorry its not much help to you.
-
-
9th July 2010, 11:48 AM #4 
Originally Posted by
kili
IP CONFLICT?
The dialog box should appear saying about an IP conflict, but also I released and renewed the IP address which should resolve a conflict

Originally Posted by
CHR1S
I had this happen on a new server just this week while downloading and installing new updates. It fixed the issue itself after a restart so didn't look into it any further, sorry its not much help to you.
Thanks for your reply, like all good technicians I did try a reboot.
-
-
9th July 2010, 11:53 AM #5 I don't suppose they're all connected to the same switch are they? dodgey switch?
Edit: but then that wouldn't explain why a reimage fixed it....
-
-
9th July 2010, 11:56 AM #6 Better suggestion: NIC Driver?
How about trying shoving another network card, usb wireless or whatever in one and see if that works correctly??
-
Thanks to BatchFile from:
-
9th July 2010, 11:58 AM #7 
Originally Posted by
rolfea
Thanks for your reply, like all good technicians I did try a reboot.

Do you run a software firewall? Could be random port blocking?
-
-
9th July 2010, 12:19 PM #8 One one of the affected machines have you tried resetting the IP stack just in case something has gone wrong?
netsh int ip reset (I think)
(I doubt it would fix it since you can ping and get other outside connectivity but it won't hurt).
-
-
9th July 2010, 12:23 PM #9 A release and renew will not always cure an IP conflict, if the other machine is switched off at the time, But if your using a DHCP server IP probably wont be the problem, sorry just throwing ideas in the pot
-
-
9th July 2010, 12:26 PM #10 
Originally Posted by
TonyRidal
Better suggestion: NIC Driver?
How about trying shoving another network card, usb wireless or whatever in one and see if that works correctly??
Thanks for this suggestion, I'll hunt down an external NIC and try that.

Originally Posted by
CHR1S
Do you run a software firewall? Could be random port blocking?
According to the network manager, no Firewall has been enabled or configured for the machines. It's done through our ISA Server.
-
-
9th July 2010, 12:46 PM #11 can you access your servers via IP instead of name?
-
-
9th July 2010, 12:53 PM #12 Its probably one of two things
(1) Firewall as already stated
(2) Conflicker
It is very common when installing clean PC's for them to get infected the moment they get connected to a network. It just takes one infected machine on your system and - wham ... new machine screwed.
-
-
10th July 2010, 11:24 PM #13 Possibley a rogue DHCP server. An example could be someone trying to join a wireless router to the network to try and use it as an access point.
-
-
14th July 2010, 11:36 AM #14 The problem ended up being Sophos Firewall.. thanks for all your replies.
After a Sophos update, any newly imaged machines also recieved firewall settings which were never set up by the network manager.
Thanks for your time, hope you don't feel like I've wasted it.
-
SHARE:
Similar Threads
-
By m25man in forum Networks
Replies: 6
Last Post: 5th February 2010, 10:21 AM
-
By silver in forum Networks
Replies: 11
Last Post: 27th March 2009, 04:20 PM
-
By david12345 in forum Windows
Replies: 7
Last Post: 24th April 2008, 10:07 PM
-
By Chris in forum Networks
Replies: 9
Last Post: 15th March 2006, 02:56 PM
-
Replies: 21
Last Post: 12th December 2005, 04:01 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules