Discussion Locked

cannot map to an NT stand alone server

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

Have uses logging in locally to the machine on portable laptops that cannot map to a stand alone NT server when connected to the network [tcp/ip]. If the user logs into the domain, there is no problem connecting to the server?

Any ideas?

thanks
skl

10 replies

by rgarner

Check the workgroup name under the identification tab of stand alone server. It should be the same as the domain name. Also, the local user must have the same user ID and password as their domain account.

by susan.krohn-lane

Nope, thats not it. All users when they have a local machine are setup identical to their network profiles/username/password, etc. Is very weird. The problem is only across the WAN at another site. My local users can map to stand alone users, but at our PDC location their users cannot map to their stand alones servers nor ours. Nor can I map to theirs when I log in to a local machine rather than the domain. It is like an authentication problem since it will prompt for a username and password but then deny access stating that username and password are not valid.

I am limited to what I can check on the PDC since the big honcho there does not like anyone knowing how he has it setup.

by rlardinois

It is an authentication problem. The fact that you are getting the prompt is good. As I remember, you may not get prompted under 95 but NT and 2000 will prompt you. When prompted, login as domainname\username and the password. If you want to login locally to the server, use servername\username and password. To login locally, the user must have an account on every server they need to access.

If your domain is named marconi, it would look like:

marconi\susan

by rlardinois

Are all your file and print servers member servers? Or are some members of the domain and some members of a workgroup?

by susan.krohn-lane

Needed local login rights doesn't make much sense since MS promos stand alones for file servers and prn servers..also my users can access the member servers here and I can access the standalone at an outside plant whereas their inhouse users cant. These are uses loging in locally to their laptop and then accessing resources on the net. Under 95/98, there is no problems in mapping to standalone servers. Only through NT and W2k

thanks for any imput

:)
skl

by bill cassada

I'm a little confused but I'll give it a shot here... authentication seems to be the issue. If you do not logon to a domain then that domain's resources are normally unavailable to you. If you setup the workgroup with the same name and no one has restricted your access some other way, then you can try to connect to any computer you can see....when the CONNECT AS box comes up you will need to supply a set of credentials recognized by the PDC (or BDC). This will indeed be in the format DOMAIN\USERNAME and PASSWORD. So if your DOMAIN was MYPLACE and username GURU with a password of HELLO!123 then it would look like this:

CONNECT AS: myplace\guru
PASSWORD: HELLO!123

If this doesn't work come back and let us know. Good luck!

This discussion is closed to new replies.