Wierd Network Connection Problem

[aroostook]

OK, I have this computer (Win XP SP 2 512 MB P4 2.8 GHz and all that jazz) that is very slow when it comes to connecting to web resources. Also, and this is the bigger thing here, IT WILL NOT PRINT to a network printer (shared or otherwise). Instead, the print screen will hang (sometimes it will outright say it cannot print at all). The computer WILL print to a local printer, so I don't think it's the spooler. I've done a SFC, verifier.exe and 2 netsh reset commands (interface and winsock...I just pulled them out of my rear as a last resort). I'm clueless as to what else I can do. The Event Viewer does nothing for me (no warnings at all).

Any help will be greatly appreciated.

 

[BadBigBen]

have you tried uninstalling the NIC and have windows install it again, also how about updating the drivers for the NIC...



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[G0AOZ]

You said, "is very slow when it comes to connecting to web resources." Do we assume you're comparing it with another machine in order to make this statement?

Is this a problem that has just started, or has it always been slow and not able to network print?

If you're no further forward after having tried Ben's suggestion, check the machine out to make sure it's clean of viruses, trojans and adware/spyware etc.

ROGER - G0AOZ.

 

[aroostook]

@BigBadBen:

Yes, I have tried uninstalling the NIC, and getting new drivers.

@G0AOZ:

Yes, I'm comparing it to other machines that can print to the shared printer just fine. Printing is a new problem, but it's ability to connect to the network has always been a little slow (at least). A "ping -t" to any other network device shows that it drops packets frequently (about 1/5 of the time approximately). There are also no viruses or spyware on this machine. It had a scan done just a couple days ago.

 

[Lemon13]

have a look here

http://www.speedguide.net/Cable_modems/cable_reg_win2k.shtml

check ur mtu/mss settings

 

[JockMullin]

Hi, Aroostook

Make sure your link speed for the nic is set to the actual/true connection on the switch/hub (eg 100mbs full duplex) rather than auto-detect.

Try another cable and another network connection.

Jock

 

[aich69]

Do you have any network printers installed that are no longer in use or even part of the network? (I'm assuming you are on a doamin here connecting to printers through a print server).
If you do, deleting the obsolete printers may sort the print issue out.

I used to have a handle on life... but it broke. Cpt. Red Bull

 

[G0AOZ]

Since you have other machines to compare it against, I'm going to assume the network cable is being plugged into an RJ45 wall or floor socket maybe...

Try taking the machine to a different part of the building, or plug it directly into your switch or router. That will eliminate any issues relating to dodgy RJ45 socketry, cabling, etc.

ROGER - G0AOZ.

 

[aroostook]

Hi all, thanks for your help.

Apparently, the problem ended up being that there was some kind of interference and/or crosstalk. The computer would still send and receive data (albeit poorly) over the network...yet the cable (at the switch end) wasn't plugged in! I would've expected the usual "The cable is not plugged in" error, but it never happened. Now it's plugged in and is accessing everything just fine.

Silly little thing. I've never seen it go like this before.

 

[BadBigBen]

albeit it being a funny little mishap, I'm glad you found the problem and it was resolved...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."