TCP/IP Win2K Problem
 

Sometimes I should just leave well enough alone.

I have a Win2K desktop and a XP laptop set up through a router to my cable modem. Everything had been talking to each other and the net last time I checked (had been a while since I checked to see if the laptop saw the desktop, but it connects to the net through the router just fine).

This evening I wanted to transfer a file from desktop to laptop while sitting at the laptop. Noticed that my network workgroup wasn't showing up. Didn't even show the laptop in the network from the laptop. Desktop was seeing everything fine. In working out this problem I created a worse one.

Had everything seeing everything but my filesharing on my desktop just wouldn't kick in. Everything I read said to uninstall and reinstall the tcp/ip protocol from the network adapter. Uninstalled.. asked to reboot... rebooted, reinstalled (didn't ask to reboot). Did this several times. Now the desktop can't see shyt. Not the router, not the laptop or the net. I even tried taking the router out of the loop and connecting straight into the cable modem. It won't grab a proper IP. It's like somethings wrong with DHCP or TCP/IP.

Any suggestions?

Congrats :thumbsup

put the ip manually like 192.168.0.1 and 192.168.0.2 for eachand subnetmask 255.255.255.0 and share the desktop again.

I can see the router when I do that, but not the internet.

PK,

What version of XP do you have on the laptop?

You mentioned reinstalling the TCP/IP protocol for the network adapter. Did you just install TCP/IP or did you uninstall the network adapter from Device Manager? That might be your next step.

SF

It's not on the laptop..it's my desktop which is running Win2K. I started with the protocol, the tried removing and re-adding the adapter. Messed with this dang thing for 6 hours. Now I'm stuck doing my update on my laptop.

Thank goodness for the 1gig jumpdrive that my brother bought me for Xmas. I thought it was a dumb gift that I'd never use, but it's the only way for me to transfer working files from my desktop to my laptop right now.

I asked about the laptop because I wasnt sure if SP2 was blocking your seeing the desktop.

Sounds like you have a temporary fix. I could come over if you need some more help with your uh, Windows. :winkwink:

Set your 'puters to 192.168.0.2 and .3, and in the TCP/IP config set the gateway to 192.168.0.1 - this should be your router.

Cycle/reboot the router. Log into the router with your web browser and make sure it got an IP from the cable provider. If it did not, cycle/reboot the cable modem, then the router. Once the router has an IP on the WAN side, you should be able to see everything.

here kitty kitty

Q: What is the manufacturer of your Broadband Router?
Q: Do you manually configure the IP address, netmask, gateway, etc. or do you use DHCP? If DHCP, is that served by your router?

If you don't use DHCP:
Q: When you re-install the TCP/IP stack don't you have to re-configure the card by entering the IP details again?
Q: What are the IP settings of your laptop? Do "ipconig /all" in command prompt and paste the settings here

Done all this twice.. Using the numbers from the router through my laptop to change the settings on my desktop. I can ping the router from the desktop but can't get the management tool page to open in the browser. When I go back to automatically obtaining I can't ping the router.

First.. all this on my desktop worked until I uninstalled and reinstalled the tcp/ip protocol on the desktop. The laptop is still working fine through the router.

From what I can figure with Win2k it seems like my DHCP server is missing and subsequently can't find the router and assigns it's own ip address.

Have you checked to see if the DHCP client is running on the desktop? Control Panel/Administrative Tools/Services and make sure the DHCP client is on Automatic and is running.

you can manually assign the ip on your desktop dhcp is not needed in a 2 computer workgoup.

it is on automatic and running

I have done this several times. When finished I can ping the router, but can't get to it through a browser and I can't connect to the net.

Had a similar encounter with a small network. They had Verizon DSL, and when you unplug the router, the DSL password changes. You had to call Verizon for the new pw.

You mention that you have a cable modem, so I dont think this is the solution for you. If you cannot connect to the net from either PC (and tcpip is working), id recommend calling your ISP and get new IP settings.

You could also try removing both the Client and Tcp/Ip from the stack. Then reinstall if that doesn't work you could remove winsock and winsock 2 from the registry.

Can you ping IP adresses? google.com is 216.239.37.99 ... try that and then try pinging google.com. If the IP works and not the domain name it's a DNS issue. You don't have kazaa on your machine or similar do you?

ALso, is anything in your hosts file? In C:\WINNT\system32\drivers\etc\hosts.

Rebuilt the stack twice. If I remove winsock from the registry does it reobtain it on reboot?

Nope.. it's not just a dns problem. Can see shyt with it on autoconfig. Get a DCHP 1006 error in the event viewer and it sets its own IP outside of the routers numbers (completely different). When I put in my own IP, gateway, etc.. I can ping the router, but can't get to it on my browser. Even tried forcing the entries needed in the registry but they go back to the original on reboot.

I take it you've already scanned for spyware and browser hijackers?

I'd be curious what an IPCONFIG /all looked like in your current state....if you have no problems posting it or feel free to ICQ 266835420 if ya want someone to walk through some things

Looks like it's working now.

Uninstalled the tcp/ip protocol from the network adapter for the umpteenth time. Then deleted the registry keys for winsock and winsock2. Rebooted and reinstalled the tcp/ip and voila.

not only fixed the dhcp problem, getting to the net and the router.. but fixed the original issue that I was troubleshooting before all of this... getting the laptop and the desktop to see the desktop on the network and be able to access it.

Thanks all.