Problems with printer & file sharing between XP and 98SE systems

[bobmcb]

I have 2 Win XP Home edition and 2 Win 98SE systems networked with ethernet using a Linksys router and a
speedstream DSL modem for internet access.

If the XP machines are NOT turned on, the Win 98SE machines can see each other and the internet and file and printer sharing work correctly.

If either or both XP machines are on, then Network neighborhood can not find the other Win 98 machine or the XP machine(s). An XP machine can find just one of the Win 98 machines, always the same one. The XP machine can also get to the printer on that Win98 machine. Internet access works just fine from all machines all the time, regardless of what is on or off. Workgroup name same on all machines.

Does anyone have any ideas, or perhaps the details of just what protocols must be defined when XP and 98 machines are trying to work together. TCP/IP must be OK since internet stuff is always OK.

Thanks,
Bob McBirney
bobmcb@sbcglobal.net

 

[bcastner]

Disable the "Computer Browser" service on the XP machines. There are other alternatives, such as setting the XPs not force a new Master Browser election.

See Bob Linn's notes on Workgroup, and Browser Issues under the Troubleshooting section of his Chicago Tech site:

http://www.chicagotech.net/

 

[Arin]

Local networking in Microsoft OSes doesn't use TCP/IP, it uses it's own special protocol. In WinXP, it's called NetBoui, while in XP it's called NetBIOS. First guess, make sure you have that protocol installed properly on all four machines (specifically the XP machines), and make sure that they're all on the same workgroup (it sounds like they are, since every one of them has seen another one at /some/ point). Once that's done, make sure you've got at least one folder set up as shared on each computer, sometimes a computer won't go on the list if there isn't at least /one/ folder with share priveledges.

Those are the things I'd try. Hope they help.

Jerry Castaldo

 

[bcastner]

Arin,

Quote: "Local networking in Microsoft OSes doesn't use TCP/IP, it uses it's own special protocol. In WinXP, it's called NetBoui, while in XP it's called NetBIOS."

. Netbui is one choice. There are other protocals supported under Windows Networking, including the older Netware IPX, the older AppleNet, DLC, etc.

. Prior to Win2k, Netbios in one form or another, was the primary name resolution method for Windows. It is included still with XP (including a non-TCP/IP transport, Netbui) for comptability reasons.

. You can run pure TCP/IP networks under Win2k and XP, the issues is whether with a mix of older OS clients you can run pure TCP/IP networks. Most practical experience has been that it is easier to enable Netbios over TCP/IP in the client setups.

. Occasionally with a mix of Win95x, Win98x, NT, Win2k and XP in mixed settings, it is just easier to run Netbui. It solves a lot of browser issues. See, for example, Scott Finney's notes on this:

http://www.scotsnewsletter.com/40.htm#tipadaweek

. A lot of existing network admins find it a lot easier to just resolve name browser issues and continue to enable Netbios over TCP/IP in Windows settings. It can be tricky at times. Bob Linn's site, cited earlier above, has some practical tips for dealing with these issues.

My own rough suggestion: In small LANs with a mix of Win9x clients, Win2k & XP either:

. Have one machine always on, and make it unambiguously the master browser;

. Disable or modify the browser status of the "superior" browsers set by default; namely, modify the Win2k and XP clients so that they do not force browser elections every time they are turned on.

. Or turn off the Computer Browser service on all Win2k and XP clients.