Discussion Locked

win2k Pro in NT domain

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a stand alone server (own domain) in an NT network.I want to copy files from my win2k pro to it but I can't. I can't browse to my pc, but I can from my pc to the server, I can't add users from that server because it doesn't appear in the drop down list. I'm sure is something simple ,but, I'm missing it. Thanx for the help.

14 replies

by gigelul

Maybe this stand alone server don't have own domain and is only started with a local account. See in logon screen if you have the possibility to start it in NT network domain (change "own domain" with NT network domain).
If is true that it have an own domain you must establish a trust relationship for these two domain.

by gigelul

I missunderstood something.
Win2K Pro is an workstation OS. Win2k Server is a seperate product.
You upgrade an Win98 to Win2k Pro and this is your "stand alone server"?
If this is the situation remove from Server manager the name of this computer then go to this computer and login with local admin account.
In network properties change to workgroup and reboot computer.
Login again with local admin and change to your domain. Also enable option and give the name and password of the Domain Admin account.

by curlergirl

It sounds like maybe you don't have file and printer sharing turned on on your Win2K Pro workstation. This is necessary in Win2K Pro (unlike NT) in order to browse the machine from any other machine on the network and copy files from it. Also, if the Win2K server is in its own domain and is not a member of the same domain as the NT server, then you might not have rights to the Win2K server's domain. Maybe I'm not understanding correctly how it's set up, but it sounds like there is no trust relationship between the two domains, in which case you wouldn't have any rights on the Win2K server. Hope this helps!

by fakeadmin

Before the upgrade from W98, I was able to browse from and to the stand alone, I doubt trust relations is the problem. Now I can do the same from everywhere else in the network ( exclusively win NT and W98 wksts) but not when I'm in front of the stand alone. I get the " "logging as \\username and pswrd" prompt. Not administrator's or local user's worked.No problems when I seat at my wkst and browse to the stand alone. Any more ideas we'll be appreciated.

by harness

If you can monitor the ports your NT 4 server is using, check and see whether TCP port 445 is listening for traffic (netstat -na at the server). If there's a "LISTEN" for 445, try to disable it. I recently had a similar problem, and found that 2000 Pro browses first via 445. If it gets a response, it thinks the browsed server is a 2000 server and continues using 445 (which won't work for an NT 4 server). If no response is received on port 445, 2000 Pro tries again on port 139 (the proper port to browse an NT 4 server). Once I stopped the access on 445, 139 took over and browsing, mapping, and file transfers worked.

by tora

I agree with answer 2. You'll need to ensure that file & print sharing services are installed on your W2K Pro PC.
Hope that this helps.

JT

by fakeadmin

Thanx to your sugestions, I stumbled into the answer. when I upgraded from W98, what was my user name became "administrator" (on the local machine. Therefore, when I tried to browse onto the w2k pc from the NT server, my user name would not be authorized. The only local users where "administrator" and guest(disabled. By creating a new local user I was able to log onfrom the stand alone.Mind you, this wasn't necessary from any other pc or server in the same domain as my PC.

This discussion is closed to new replies.