not a huge deal but I dont like loose ends

[DrewsNick]

problem: I cannot log onto the network on my system

info about: I can "search for my wifes system and see it fine, I cannot search and find mine tho. My wifes system could see mine too. Its not a big deal because I can use the search to open her box and pull files and all that.

equipment used: windows me on both boxes, linsys fast network in a box kit from wally world (walmart). att@home service.

I followed through the whole network trouble shooting wizard like 3 times and still no good. I just built the new system listed on the MyRig link at the bottom of this post. The network was fine on the old system.

ya'lls think I should rip the protocols out of the both systems and set mine up first then make the stupid floppy disk and run that on her system?

how bout a straight up tcp/ip network setup? is it better? is it faster? will I have issues with the att@home service doin the tcp/ip?

the option is to do the ipx/spx nebui thingy I had before.

 

[cz]

Is is possible that one machine has NetBEUI and the other does not? Both machine should have the same list of networking protocols to work together properly.

 

[DrewsNick]

I am sure it does but I cannot verify from here as I am at work. I did the instructions exactly as in the linksys kits booklet and it worked on the previous box. this time I ran the floppy from the wifes box as per the me directions. and as part of my troubleshooting it all looked right as rain.

I dont get a network not available error I get a cannot access the network due to an unknow error.

how bout that tcp/ip network? is that challenging? is it more stable? faster?

 

[cz]

I would say that TCP/IP performance is just as good as NetBEUI. Only reason that you might need NetBEUI is that some old applications do not support TCP/IP.