Newbie help pls - win2k workstations won't logon

[NC35]

I am sorry as I am sure that ths topic has been covered elsewhere, but after a keyword search I couldn't find much.

I am trying to get experience with Win2k Server from text book and practical experience. I have a server which will install W2k server no problem. I also have a notebook and workstation both w2k pro. If I continue with the config server wizzard after first boot the ADS is automatically installed and a domain server (.local) is set up. After this i can't find the server from the workstations. If I leave the server as a workgroup server all is fine. I assume that I have configured the IP's etc ok for the workgroup to be ok.

Question what do i have to do to get the domain server etc to work with the W2k workstations? Sorry if it is something simple or if I have not included enough info.

Any suggestions more than appreciated, before I delete the partition and reinstall again :0)

Thanks

Lee

 

[degreat]

Right Click on my computer on the workstation. Select the Network identification tab. Then It'll give your the choice to join the server.

Try this first.

Shan

 

[tlcscousin]

Can you ping the server from any of the w2k pro systems?
If not run ipconfig /all and check the ip addresses on the pro pc's and make sure they are all in the same subnet.
If they are not you will have to set their addresses statically or set up dhcp and scopes.You can set up reservations so they always get the same addresses.
If they were previously set to obtain an ip automatically and the server was set statically with no dhcp running there is little chance of seeing each other.

 

[CybX09]

Something that got me a few times, is after you join the selected network and then reboot click on the advanced button to make sure that the correct domain is selected. Many times I have checked this setting and it is set to logon to the "local", which is just logging onto the PC not the network.

Hope this helps.

 

[yizhar]

HI!

Make sure that the W2K clients use the DNS server on your server in network settings.
W2K relies on DNS for name resolution.

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[NC35]

Thanks for all you suggestions.

Yes I have tried the Network ID (but from control panel/system) when domain (xyz.local) is offered the server domain is not recognised, or sometines it asks for the administrator password to register the account. On rebook the workstation takes forever to reboot registering settings etc (

Yes the workstations can ping the server and the server can see the workstations no problem.

Yes I have discovered the local/domain option sometimes local is the only way to get ontothe workstation.

If the server has the scopes set up can the workstations obtain the IP address, sub mask and preferred DNS automatically?

Thanks again

Lee

 

[tlcscousin]

If the scopes are setup yes the workstations will get the proper info from the server.

 

[Tels]

Like everyone say, ping to make sure a connection actually exists - then....

Log on to the Win2k client locally, and if you go to network&dial up connections, you should be able to fill in the box with your servers domain name... It should then ask you for an account name/password with administration rights to the server. What you enter here is ideally the administrator account details for the server - not the local computer. This will allow the server to automatically create an account for the computer you are connecting.

If that fails, go to the server, open Active D. Users and Computers (mmc snap-in), and add a computer. The name should be the same as the client you want to connect.

If you go back now and connect the client again, there should be no delay as you have manually created an account for that computer, if you have been thus far successful you'll have to restart.

When you log-in make sure you use a domain account and password - not a local account and password.
(You can be sure by using your (servers) administrator user/password combo and make sure the domain is selected in the login option box)

Good luck... that should work.

Tels

 

[NC35]

Thanks to everyone.

I had gone through all your suggestions already, but it is nice to know that I am on the right path.

Anyhow finally traced it back to a faulty nic!!

replaced it with a new one the whole system (inc workstations) started running on "light speed" ;0)

Thanks again

Lee