Laptop TCP/IP Problem
Author
Discussion

bigdods

Original Poster:

7,175 posts

257 months

Sunday 26th February 2006
quotequote all
Neighbour has handed me her laptop ... wont connect on the wireless. So I plug it into my switch and it wont work on ethernet either. Its not getting an address thru DHCP so its using what I think is one of the internal defaults 169.254.175.161 255.255.0.0 with no default gateway. If I hard assign what I know is correct address it pings , but throws some odd text on the screen before it starts seeing responses...and IE still doesnt work. Sounds like the TCP/IP stack is busted to me, but I cant for the life of me remember how to remove and re-install. In the networks settings I cant uninstall TCP/IP - the option is greyed out

Help.....

edited to add: If I got to CMD , and use ipconfig /renew I get the following text: AN error ocurred while renewing interfact local area connection 3: an operation was attempted on somthing that is not a socket.

Just for good measure I have uninstalled and reinstalled the devices, problem persists

ANd edited again: now I have allowed my alcohol soaked brain time to think of course its obvious - winsock it broken - ran the fix and all working now

Moral of the story - dont drink and attempt to fix PCs at the same time lol

Dodsy

>> Edited by bigdods on Sunday 26th February 20:52

>> Edited by bigdods on Sunday 26th February 21:09

aldi

9,288 posts

267 months

Sunday 26th February 2006
quotequote all
You missed out some important info... is she pretty?

griffgrog

740 posts

276 months

__LEE__

7,520 posts

273 months

Sunday 26th February 2006
quotequote all
Good Fix

nlldavies

270 posts

261 months

Monday 27th February 2006
quotequote all
Try the following at the command prompt:

netsh interface ip reset all

It should rebuild the TCP/IP

bigdods

Original Poster:

7,175 posts

257 months

Monday 27th February 2006
quotequote all
Just to close this down- I had answered my own question about 5 minutes after I posted it (once I let my alcohol sodden brain engage properly)

It was a corrupted Winsock - the fix as ever is (from the cmd prompt) : netsh winsock reset