Network computers see/don't see each other

Hey Rockster, I remember in another post you talking about difficulty removing Norton AV. Norton has published a uninstall program you can download from the Symantic site. This is supposed to clean up the garbage that System Works leaves behind, including NAV. Since I haven't uninstalled it, I can't tell you if it will take off AV without System Works being installed, but it might be worth a try. I have it in a zip file which I'll be happy to send to you as an email attachment if you want, or you could go to their site and download, it is about 200KB.

 

As cold as it's here (Central WI) a drink would do good. But I found out in my 20's (many, many moons ago), dry heaves, hangovers, zombia like for 2 days plus... all on 2 to 3 drinks... alcohol did not agree me. Even though I tried like H E L L to convince my stomach I knew better... for the next 10 years. I finally gave it up, spend what I saved on computers / toys and a soda now and then. But being frugal, I can set you two up for all the "Saint Pauli Girl" you can send down the hatch. Just tell me the recipe, you two can do the rest.
Yep, I have a Linksys. Yep, I knew you had a DLink from the start of the post. I was just giving suggestions, hoping there was some cross-over in the the brands. As far as printed manuals, do they still do that?!!

 

Martin,

I too have confidence. You'll get there!

D-Link Support. Select DI in first window, 614+ in second. Manual available in PDF.

 

Sidebar off topic

Martin: might have said that ? but I have no problem removing NAV, LU & Live Reg, all corresponding registry entries, shared files and application data manually. Also have two different little uninstall programs from Symantec. Thanks though. I'll never turn away help or guidance from any quarter.

 

Just for clairification he said in his earlier post that he had a "D LINK ROUTER"

The username is admin
The password is left empty
the address to get there is 192.168.0.1

Yall got the man so confused he thought he had a Linksys by the time I read this

martinr121,
Dont go back under the house just for diagnostic purposes, just run the cable through the house.
Are you buying pre made cables or are you putting on the ends your self?

Not seeing one of the other computers on the network is a diffrent issue than getting to the internet. Dont confuse the 2.

Worry about getting them to see the internet first, then address the issue of not seeing each other second.

 

Ah, the mysteries of computing. Last night, no matter what I did I could not get the D-link settings open, would not accept anything I entered in the dialog box for user name and/or password. This morning, one more desperate attempt, typed in "admin" and wallah, it opened.

So then I'm mucking around through the settings and see nothing that would help with getting computer C to start working properly. As this machine, A, and B, daughter's don't have a problem, it is clear that the fault is somwhere in C. (son's machine)

The D-Link site (thanks Noahdfear) led me to the Practically Networked site where I found (edited for brevity) this:

"Typically the only time you would get an IP address beginning with a 169 is when the PC is not communicating with the DHCP server.

Go into your network properties and remove all of the networking components that are installed there.

This usually includes things like the Network adapter drivers, the various communication protocols (e.g. TCP/IP, IPX/SPX, NetBEUI), and the network client. Once all of these items have been removed, you’ll be forced to reboot the system. After the system reboots, reinstall the network adapter drivers, which should also install any additional components you might need. After the system reboots again, your TCP/IP protocol stack should be functioning correctly. "

Which is pretty much what Newt advised. But, didn't my physically removing the adapter and deleting it in device manager accomplish the same thing??

If not, once the device is removed, as far as I can find, there are no network settings, or are there and I just don't know where to look??

The article goes on to state that the cause is usually a virus or spyware. He had plenty of that on his machine. Also, re-install XP will fix it the article says: "almost guarantee" Hmmmm.

If nobody says anything else I should try, that's what I'm going to do, re-install. Question, on the re-install, leave the network card in or add it after??

AARRRRRGH! Where is the emoticon for total frustration?

Martin

Edit: I think I'll try a repair from CD with XP running, see what happens.

Sidebar off topic:

Rockster, My memory is somewhat faulty, my wife says I have Partsheimer's disease. Somebody on this board was complaining about NAV removal difficulties, must not have been you, sorry.

 

ssmith10pn: thanks for chiming in on this.

Confusion is my normal state of mind. They didn't do it to me, I did it to myself, I came to believe I had a Linksys router, can't figure out where THAT came from.

Anyhow, the first cable was made up for me at Radio Shack. The new one I bought pre made at WalMart, it is from Belkin. But for sure it doesn't seem to be a hardware problem.

Like I said, I'm going to try a repair install and see what happens.

 

Martin:

I wouldn't advise re-installing just for the networking - you can add all that you need back into that machines network configuration by just selecting add and the appropriate protocol, service whatever - use another machine for guidance if its somewhat confusing. However, based on what you said about #1 son's machine being loaded with crapola before you cleaned it up, you may be well advised to re-format and re-install.

As to the partshiemers, I thought your wife was still treating you for acute stubbornitis. Regardless, as a refresher, we went through your Soyo boot sequence,RAID configuration and Bios together a couple of months ago with Mattman and PeteC.

 

Try this. http://www.cexx.org/lspfix.htm You don't mention any winsock errors just 169. ip but you have removed a bunch of stuff and this can mess up winsock a real essential part of any networking. Either this or a new card.

 

Rockster: The stubornitis is hereditary, so I just can't help it.

Maggie: thanks for the link, I downloaded it to this machine will copy to CD to machine C & give it a go.

One thing I just discovered, I did an install of XP on that machine, and I thought it was going to wipe the drive, it did not.

I did not uses the Upgrade choice, but the OS preserved everything on the machine. Including programs and faulty networking. Still getting the 169.xxx.x.x IP address.

That install just created more problems, I can't identify the AGP card, even after taking it out and examining. I've had so darn many cards, got a stack of CD's for cards, none seem to work. I'm going to try and find the Universal N.Vida drivers & see if they will work.

Will post back when the winsock repair has run.

XXXXX Those are crossed fingers.

Martin

 

Maggie: I wish you were standing next to me so I could give you a big hug and kiss!!!

The Winsock Repair worked!!!!!!

Both internet and LAN are working like a charm.

Anybody who has a network should download this program, free, fixed my LAN like 123.

Maggie, I can't thank you enough.

Same for all who helped me through this nightmare.

Martin

 

Your very welcome. I keep a download of that just in case.

 

Sounds like you may have an issue with TCP/IP stack or most likely with winsocket

Try this:

1) Under local area connection general tab , Uninstall all the components listed under "This connnection uses the following items "

DO not reboot the system if asked.

2) Remove the NIC drivers

3) Delete the Winsock and Winsock2 key in the registry under:

MAKE sure to BACK UP THE REGISTRY KEY

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\

Exit the registy, reboot the system, reinstall the NIC, make sure that the networking components are back "Under local area connection " test...

 

PC_WIZ: Hey, thanks for the comeback on this. Right now, all network functional, I won't mess with it. Maggie's "winsock repair" fixed it w/o telling me how. It just went through the settings and repaired them. It does report files it changed, added, deleted, but again, might as well be in sanskrit for my understanding of it

Anybody using networking should have a copy of this file and try it first. (www.cexx.org/lspfix.htm) The number one fix as far as I am concerned. Works even for the "ignorance of networking" like me.

I am printing out a copy of your post, put it into my folder "Bag of tricks" for networking. Will keep it handy should networking go south again and Winsock Repair fails, I'll go through the steps you outlined.

Thanks again and thanks to all that helped. Thanks to this great board, the best on the net. Pay your dues, be a contributing memeber, keep it working.

Martin

 

martinr121

Something that I ran into.

Seing the address C: 169.254.180.119 rang a bell loud and clear.

That is the same address that one of my PCs was using ( or showing ) when I tried to use a D-Link Router.

It would acces the Internet but network games between it and the other two PCs would not work. HHMMMM !!!. What happened . They have been working for YEARS.

I went back to a newer Linksys BEFSR41 Router and the problems left the scene immediately. With no help from me.

No problem in over a week now. All PCs see each other. ALL games play with no hasseles.

I will agree there. I should have listened to that BEFORE I tried to make things better and wound up breaking them.

BillyBob