Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

uninstalling tcp/ip in workstation

Status
Not open for further replies.
Aug 15, 2002
31
US
i'm at a bit of a loss here. i have a customer that is converting his office from his corporate isdn over to cable broadband. he is an agent for a bigger corp that has been kind enough to supply me with all of their vpn, firewall software preconfigured for broadband use. one of their requirements was to put the network behind a router for NAT capability. no problem. they have 4 nt4 workstations which i switched over and loaded the software on. all but 1 of them went without a hitch. the problem system, once i loaded the software, cannot pickup an ip via dhcp. i can put a static one in but cannot do dns resolution. i can ping any ip to hell and back inside and outside the network. also, when i start the vpn client with an ip for the host i get a socket error. my thinking is simply that tcp/ip and winsock are hosed. i can get to the winsock to remove it but the system will not allow me to remove tcp/ip. i get the error 'Unable to remove namespace provider'. i have tried unbinding tcp from everything, same result. my question is, should i uninstall the nic and remove the vpn software (as it installs an extranet adapter) and then see if it will remove tcp for me? or does anyone else have any better ideas? i know it can't be an error with the vpn software as it worked fine with all the other systems using the same OS. i'm just guessing it didn't like this one. i am getting no help with the customers corporate tech as they are not responsible for supporting their agents, they are on their own. all i got from them was 'sounds like a tcp/ip problem any help is very much appreciated.
 
I'd try Service Packing the box (again) first, as this should update a lot of the core TCP/IP and networking files. [auto] MCSE NT4/W2K
 
I just went through basically this same thing on an XP Laptop. I could ping "from" the laptop but not to it. Remove the VPN client and get pint to respond like it should. Then reinstall the VPN client.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top