rolfea Posted July 9, 2010 Posted July 9, 2010 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?
CHR1S Posted July 9, 2010 Posted July 9, 2010 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.
rolfea Posted July 9, 2010 Author Posted July 9, 2010 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 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.
BatchFile Posted July 9, 2010 Posted July 9, 2010 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....
BatchFile Posted July 9, 2010 Posted July 9, 2010 Better suggestion: NIC Driver? How about trying shoving another network card, usb wireless or whatever in one and see if that works correctly?? 1
CHR1S Posted July 9, 2010 Posted July 9, 2010 Thanks for your reply, like all good technicians I did try a reboot. Do you run a software firewall? Could be random port blocking? 1
ajs Posted July 9, 2010 Posted July 9, 2010 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). 1
kili Posted July 9, 2010 Posted July 9, 2010 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 1
rolfea Posted July 9, 2010 Author Posted July 9, 2010 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. 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.
zippo Posted July 9, 2010 Posted July 9, 2010 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. 1
RobMongoose Posted July 10, 2010 Posted July 10, 2010 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.
rolfea Posted July 14, 2010 Author Posted July 14, 2010 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.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now