Mixed OS on Network

This is a continuation of my previous posting regarding Win98SE computer being "invisible" to the network.

Does Windows 2000 server write something to a Windows 98 OS causing that system to be disconnected from the network if the Windows 2000 system is not running?

My machine running Win98 (Ginger) shows up fine with Windows 2000 server (Alice) operational, but not when the I replace the win2000 server OS Drive in the "Alice" machine with a drive running Win98SE.

The "Ginger" machine showed up properly in the network before it ran in concert with Windows 2000 server so I must conclude something was written somewhere to inhibit the "Ginger" machine from the network when Windows 2000 server is not running on the "Alice" machine.

I'm reasonably sure that if I wipe the OS completely on the Ginger machine and reinstall, it will show up on the network without Windows 2000 server running, but that would require a lot of time and work what with reinstallation of all the devices and apps ... and it still would not solve the mystery. Also, the problem would re-occur when I again put this system on the network with 2000 server running.

Does anyone know if there is a file I can delete or edit to fix this problem or is it just another "Microsoft Secret" ?

 

When "Ginger" is logging on to the server, is it logging onto a domain? Once you switch the OS to Win98 on the server it is no longer using a network domain and is using a peer network. Is the workgroup name consistent between Win98 and 2000?

 

Thanks for the response.

Not a domain. Workgroup name is consistant when Win98SE is running on both Ginger and Alice.

 

I finally found someone who gave me the tip that solved this problem of mixed OS on a network and a system not being recognized!

The problem is caused by the Win98 worksstation expecting to get an IP address from Win2K Server. If Win2K server is not running the workstation is not recognized by the network.

Running WINIPCFG and clicking "Release all" and renewing solves the problem.

I am amazed there is so little documentation on this utility.