Discussion Locked

win98 workstn to w2k server

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
i have w2k on a poweredge server networked to a single w98 workstn. I am able to log the 98 workstn on to the server and the terminal services client connection appears to be okay as well. I am able to see the server in network neighbourhood on the wrkstn. However, when i try to find the 98 wrkstn on the network neighbourhood on the server or the find computer function it does not appear. strangely enough they are both "pingable" from either end. They are both on same workgroups etc and i have tried specifing ip numbers but to no avail. i beleive it is something to do with w98 using wins etc and the server usind dhcp however i would be gratful if someone could confirm this to me with a solution.

7 replies

by bhostmeyer

Do this. Do a find computer on the network, when it finds it see if you can browse the folders on the other machine. If you can y ou need to install wins on the 2000 server.

I had this problem when we first setup the system. The problems was the 2000 server was set up to be on the network. I fixed this by NOT making it a BDC or PDC. This way it used the wins of the PDC. If you do not have wins setup on the 2000 server I would set up one.

You should only use DNS when your on a 2000 only network or when your using a subneted domain.

Hope this helps

Brooke Hostmeyer

by tony.colgrove

You need to have file and print sharing installed on the Win98 box for it to show up in network neighborhood.

by oridjinn

First: You need to have file and print sharing enabled

Second: You need to setup DNS to allow dynamic updates so that the Win98 machine will register in DNS with Win2k. DNS has basically replaced WINs in Win2K so the Win2K machine will look toDNS for the computer.

This discussion is closed to new replies.