NIC can receive but not send

LSPFIX
Download the LSPFix utility from http://www.cexx.org/lspfix.htm

Antivirus may have deleted winsock hijacker and now you cannot get it back.

http://www.cit.cornell.edu/computer/security/spyware/lspfix/

 

Speedstep,

Would either of your links (above) pertain to mine

http://forums.us.dell.com/supportforums/board/message?board.id=oplex_network&message.id=6303

?

LSPfix won't work if he already ran WinsockXPFix

LSP fix essentially re-numbers the Layered Service Providers chain if it is broken. It also has the ability to remove an entry from the registry if you check, "I Know what I am doing"

Their are two that are super critical and one that is important and should never be removed.


Winsock Fix deletes the entire LSP Chain in the registry and creates a brand new one by using the default Widnows Chain. Essentially it deletes then imports some registry entries.


LSP fix will not help you if WinsockXPFix didn't help.



________________


LSP Fix is a better program, IMO because it does not reset you 100% to defaults. For instance, if you are on a Novell Network or run Google Desktop for some reason, LSP fix won't hose you up by removing all non-default entries.

He more than likely got a driver update/bad driver or something.

It should be easy to fix. Quite simply, remove McAfee and turn off all windows firewalls and go to add/remove programs and uninstall any drivers in there then delete through device manager and reboot.

They should be auto detected or you may hae to install them. At any rate install known good NIC drivers and Windows will install clients... protocols...

Hi,

 

LSP didn't change anything.

 

I had already removed McAfee (most likely the problem in the first place - Whay is AV softwae so buggy???).

 

I physically removed the nic, deleted the driver and rebooted.  I shut down, physically reinstalled teh nic and loaded the newest driver.

 

No help.

I'm just going to reformat the drive and move on to XP.

 

Thanks for all the advice.

Jim

That should definitly fix it. Still, I think you must be missing something because I have fixed hundreds of network issues. None really required a re-install of Widnows.

Typically, I troubleshoot Adapter, Protocol, Clients, then services in that order.

I work my way up the OSI model

Application
Presentation
Session
Transfer
Network
Data-Link
Physical


Essentially, this is the blueprint for networking. It dictates if you start at the botom Physical you should first check cabling, link lights, network card hardware, and NIC Drivers to make the hardware work.

Next, you should move up a notch to see if Ethernet itself works by verifying ARP is working correctly with Media Access Lists Addresses.

Next, we check TCP/IP by pinging an IP address typically. This also verifies ARP and Ehthernet... Obviously, if we have a failure here, we re-install TCP/IP and possibly rebuild the winsock if corrupt. We need to get Internet Protocol (TCP/IP) working at this point. Obviously, the next step is to ping by name wheather that be a computername or hostname (NetBIOS DNS). We want to ensure we are able to convert names to ips. I.e. if you have a webserver named "bob" and it has an ip of 10.1.2.25 on a local intranet and you can ping its ip but not the name bob, then DNS needs to be checked out. If DNS is malfuctioning, a lot of things won't work. For instance, DNS may have the wrong DNS Suffix, it may have the worng IP addresses for DNS servers...DHCP may be configureing the clients wrong...

Next, we check the upper layers by testing the Networking Client itself. Typically this is "The Client for Microsoft Networks." A really simple test is to use a UNC path or test an application.

It should work.

-Justin

Justin,

You got me thinking. I didn't check ARP. I forget what the command sequence is to stop and restart ARP. Can you remind me?

Thanks,
Jim

ARP is Address Resolution Protocol.

I am nearly certain it is working. I have yet to see it fail. Anyway, the command is arp to check out your arp tables...