TCP/IP continually self destructs on home network.

[markjs]

I have two computers both running Windows XP Professional on a network over a 10/100 router, and they always work fine when I set up windows, but eventually and I mean every single freaking time I have set up Windows, TCP/IP fails to work and neither computer can share files anymore. I can only get the file sharing back by installing IPX/SPX, and thats not right! How do I completely remove TCP/IP and reinstall it? I think this will be the only way to get it to work again. This is not my first post and we have tried many things. I know for a fact that all the network settings (ie. IP and Subnet mask and such ) are correct so do not suggest otherwise, because I know they are correct and had worked fine up to the point at which they stopped and no changes have been made. Any other help will be appreciated.

Edited to add: It's not firewall either because I use zone alarm and all the IPs on the network are allowed traffic and if it was the firewall IPX/SPX wouldn't work either.

 

[spidey07]

you have a configuration error...check your settings.

I'm serious.

Or just install netbeui and never have trouble again.

 

[markjs]

If I had a configuration error then why does IPX/SPX work fine? And how does one install netbeui, when it is not one of the choices in XP under protocols?

 

[spidey07]

because sharing with tcp/IP is completely separate from ipx...two completely different processes. In order for sharing to work with tcp/ip every single thing has to be just right....everything (and there's about 20 of them).

If you're having trouble getting TCP sharing to work (don't worry...its not you...sometimes MS sharing just up and decides not to work reliably) then using netbeui is a great work around. Generally ipx shouldn't even be on a network card unless some arcane game needs it.

hopefully jackMDS will come along with his FAQ links

hope that helps.

 

[AFB]

Because IPX/SPX isn't TCP/IP.

 

[dmcowen674]

Originally posted by: spidey07
because sharing with tcp/IP is completely separate from ipx...two completely different processes. In order for sharing to work with tcp/ip every single thing has to be just right....everything (and there's about 20 of them).

If you're having trouble getting TCP sharing to work (don't worry...its not you...sometimes MS sharing just up and decides not to work reliably) then using netbeui is a great work around. Generally ipx shouldn't even be on a network card unless some arcane game needs it.

hopefully jackMDS will come along with his FAQ links

hope that helps.

and your protocol stack may be busted. LSP fixes that right up.

 

[markjs]

What is LSP and where do I get it?

I say my settings are correct because they were layed down at Windows install, they worked absolutely fine with TCP/IP only, and NOTHING had been changed since then unless windows update changed it.

 

[AFB]

Originally posted by: markjs
What is LSP and where do I get it?

I say my settings are correct because they were layed down at Windows install, they worked absolutely fine with TCP/IP only, and NOTHING had been changed since then unless windows update changed it.

You changed absolutly nothing. Windows did it for you.


JK, these things happen. Just calm down and lay off the bold.

 

[markjs]

Again how do I install netbeui? It is not an option when I go to install protocols!?!?

Also is there really any disadvantage in using IPX/SPX over the network? If not I suppose it's much more stable than TCP/IP.

 

[dmcowen674]

Originally posted by: markjs
Again how do I install netbeui? It is not an option when I go to install protocols!?!?

Also is there really any disadvantage in using IPX/SPX over the network? If not I suppose it's much more stable than TCP/IP.

Click on add Protocol, then under Microsoft you will see Netbeui. IPX is from the old Novell days, Windows machines really don't use it at all.

 

[markjs]

Oh thats from Win98 days. That protocol is not a part of WinXP at all. I have to go with IPX/SPX. still nobody answered my question: Is there any disadvantage to using IPX/SPX?

 

[JackMDS]

I think that WinXP is a great OS.

However it was released in 2001 and Microsoft can not predict all the future moves of Hardware and Software Manufactures that do not adhere to many Agreed upon Settings and embrace Short Cuts in order to rush to market. Windows 2003 server that was released recently to the market has a much better Network infrastructure. Some people actually configure Win2003 to work as a Desktop OS, and claim to be very Happy.

As you know Windows OS is based on a Registry that Stores almost all of the information pertaining to the Networking.

Many people use the Windows Network Wizard excessively because they do not know better.

The Wizard is very effective to be used few times in order to add new components to the Network. Repetitive usage of the Wizard in order to ?Fix? the Network Settings results in further corruption of the Network.

After repetitive use of the Wizard the TCP/IP settings in the Registry get ?Confused?, in most of the time it does not affect the capacity to use the Internet but it deem the Sharing part of the LAN unusable.

In addition, TCP/IP might get periodically "trashed" by the "Junk" dished trough the Internet (a lot of Spy Modules alter some Network related settings).

The same occurs when Network, and Internet ?Tweaking? Programs are used.

Many third party applications take the liberty of adjusting Windows Settings to what they consider the ?Best?. Their software is not aware of your specific system, and might ?adjust? few settings that are needed for other applications.

All in all, at the end the Registry end up with conflicting information, and part of Network system might not function correctly.

What are your options?

1. You can keep complaining.

2. You can Uninstall every thing and Re-Install, and hope (pray) that it will work again.

3. You can try NetBEUI (it takes 5 sec. to get rid of it if you do not like it).

Log to this page it has a lot of links to instructions to Windows Network Settings, and Sharing.

Link to: Windows Network - Installing & Sharing.

If the Manuel configuration does not help use the NETBEUI approach.

Link to: Set NetBEUI as the Default Sharing Protocol in WinXP.

 

[markjs]

Well I never used the network setting wizards so that's not my issue.

I still want to know why everyone keeps telling me about netbeui when it is not one of the choices in winxp.

I still want to know is there any disadvantage in using IPX/SPX?

 

[AFB]

netbeui is located on the windows cd.

I still want to know is there any disadvantage in using IPX/SPX?

The only problem I could see is if you wanted broadband , you would have to install TCP/IP to talk to the router.

 

[JackMDS]

In case it is Not clear.

Both TCP/IP and NetBEUI have to be installed. All Windows versions for PC can work with Multiple Protocol.

The ?Trick? is not to Bind TCP/IP to File and Printer Sharing instead bind, NetBEUI to the sharing.

As a Result the OS uses by default TCP/IP for the Interent, and NetBEUI for LAN traffic.

NETBEUI is on WinXP original CD-ROM.

Some people following the same idea use IPX/SPX, and not NetBEUI. However it seems that NetBEUI interact better with the NetBios. IPX/ISX might suddenly slow down for no apparnt reason.

Why NetBEUI helps with sharing.

NetBEUI has no settings and does not use the computer IP; it uses the computer name for identification. As a result the trashing factor mentioned above does not affect it.

So people have a choice they can adhere to Net Clichés like:

Microsoft does not support NetBEUI anymore - Yeah for home users there is nothing to support concerning NetBEUI.

NetBEUI is not efficient - Yeah it is ?silly? to use it on Big Cooperate Network (on small Networks it is actually more efficient than TCP/IP).

Why should I use NetBEUI? TCP/IP should work ? Yeah you are right keep the good work and keep complaining about not being able to share file.

Or they can install NetBEUI and SHARE. :beer:

Link to: Set NetBEUI as the Default Sharing Protocol in WinXP.

 

[scrotus]

NetBEUI for teh w!n!

 

[markjs]

I did all that it said in the link about adding NetBEUI, and file sharing still does not work!! I am at wits end. I suppose I will have to stay with IPX/SPX because it is all that works, but at this rate I am wondering when it will also fail!

 

[markjs]

No more answers? Have I baffled all the experts?

I was baffled long ago.....

 

[n0cmonkey]

Originally posted by: markjs
No more answers? Have I baffled all the experts?

I was baffled long ago.....

Please keep the taunting to a minimum.

Did you unbind TCP/IP from sharing? (I didn't check out the links, so please don't fly off the handle at me, hell half of my threads I end up answering myself )

How are you testing sharing? "My network places" or whatever it is called? If that is basically all you tried, try start -->> run -->> \\computername. For some reason that seems to work for some people when My Network Places has given up all hope.

 

[markjs]

I did unbind file and printer sharing from TCP/IP, yes.

I didn't mean that as a taunt.....I am terminally misunderstood

I will go back and try looking in more than just my network places but I am 100% confident it won't work.

 

[markjs]

I checked file sharing by typing \\jvb into IE (jvb being the other computers host name.....Nothing, dead, and gone. NetBEUI is having zero effect.

 

[markjs]

I am tempted to start a new thread but I know I'll get yelled at, so I'll just keep bumping this one in hopes of an answer!

 

[KLin]

I would start replacing hardware and cables. Cheapest to the most expensive: Cables, then nic's, then the router. I would also check out the event viewer on both machines to see if there are any networking errors that are being reported.

 

[spidey07]

Originally posted by: KLin
I would start replacing hardware and cables. Cheapest to the most expensive: Cables, then nic's, then the router. I would also check out the event viewer on both machines to see if there are any networking errors that are being reported.

lets pick markjs conundrum apart for a little bit.

If IPX work (that is a layer3 protocol) then that means the two layers below it are fine (physical, datalink or in other words the nic and cable are good)

it can't be an access problem from what I can gather.

there's something fishy with his network control panel, probably in the binding order. Probably has too many protocols on there - windows is real picky about name resolution (this is netbios at work). My guess is ipx is listed in the top of the bind.

markjs
remove all protocols except IP on all machines, reboot all machines, make sure "enable netbios over TCP" is check on all machines, reboot one machine and let it sit for 5-10 minutes then bring the other ones up.

then post the results of "net config work" and "net config server" typed from a command prompt. That will tell you exactly what windows thinks. net config workstation will tell you about the requester, net config server will tell you about the server.

 

[markjs]

I got all that except 'enable netbios over TCP'. How do I do that?