Windows Forum

Ask something
Discussion Locked

Can't See Server

0 helpful
9 replies

by wblarkin

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 3 systems which are Windows 98SE based, and an NT4.0 Server SP6. My
situation is; When I initially set this small network up, I was using a hub that
was attached to a larger network (i borrowed 4 ports and hooked each one in). I
have the NT4.0 machine as primary domain controller with the default domain name
of "domain". When I set the 3 workstations up, I had no trouble logging into the
server, using DHCP for ip address, and domain login for Windows networking. I
could see the server and all it's resources. I mapped drives and setup the
connections I would need later. (I could also see the rest of the network that
was available due to me sharing ports in a hub that was already being used).
When I moved the workstations and NT4.0 Server to a seperate hub and brought up
the systems, they still mapped the drives and connections that I setup
originally, BUT when I go to network neighborhood I can no longer see the NT
server appear and I click on Windows networking it states that the network is not
accessible in an error windows. I still have the domain login selected and it
seems to connect properly, it's just that I can no longer "see" the server appear
in network neighborhood. The NT4.0Server is still supplying the IP address for
each workstation via DHCP. Do I need DNS Server running on the Server for the
workstations to see the server name appear in network neighborhood? Thanks for
any help in advance.

9 replies

by smurfman

Agreed, with out WINS network neighbor hood is slow and dumb, and pretty much useless. If WINS is already present, try checking to the WINS settings on your windows 98 machines, and make sure they are connecting to the NT server you want not some other server that also had WINS running when you were connected to the other HUB. Additionally, check in the WINS Manager in the NT box that you have on this little network, and look for the 98 machines. If they are not there, then they are not registering in WINS properly. You could also delete the entries and let the machines relogon at their next sign on. I had one other thought that kind of concerns me, is this: When you plugged the NT PDC that you just created, into the hub, and let it connect and do it's thing...was there another PDC on the network already? Check out the NT Resource guild about having 2 PDC's on a network, I do believe that one will be shut down automatically, so this NT box, may not really be working in the capacity as you think it is. Check in server manager. Good luck...

Smurfman

by santosh

The problem seems to be with the color coding of the cable. some hubs follow standards. try changing the speed of the network card to 10 mbps at the network properties of the lancard. If this solves the problem change the color coding of your RJ45 connectors.

This discussion is closed to new replies.