[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 149
  • Last Modified:

Domain relationships??

We have a domain that has been running with NT for several years.

We upgraded our Webserver and Domain Controller about 4 months ago. Everything was fine!

I upgraded the file server to W2K last night, and everything was ok until about 10:30 this morning.

Certain W2k and NT4 workstations couldn't connect to the file server. I worked most of the day and I know what the problem is but not sure why.

There are 2 of us doing administration. The other fellow installed a couple of workstations and has the user logging in under their own domain name, not the general domain.

The question I have is this the proper way to do this? I didn't think so at the time but haven't had enough experience with this and it worked so I let it go. I reproduced the problem on my own computer. The computer browses the network alright but has no rights on the file server.

0
peterand
Asked:
peterand
1 Solution
 
deforeCommented:
If they are loggin on to the local machine only and not the domain, then they shouldn't get access to the file server. They need to log on to the domain. If they must log on to thier workstations, then they need to authenticate to the file server.

This should work.
Start>Run>cmd

net use f: \\filesever\share * /user:domain\username

f: can be whatever drive letter you want. The username has to be the one created in the NT Domain.

Hope this helps.

Steven Defore
0
 
ocon827679Commented:
Is it safe to assume that the problem children are the same ones the other admin set up?  You said logging in to their own domain, do you mean a workgroup?  I could understand how this would be a problem since they wouldn't be domain users.  
You ask if this is the proper way to do things.  It doesn't matter how many admins you have as long as everyone is on the same page.  If your not, then mayhem.  Maybe you, your co-worker and your boss need to have a chat.
0
 
JconleyMCSECommented:
You should not be logging in locally. You should be logging into the domain.

Try deleting the problem workstation's account from the domain and then rejoining the domain.
0
 
peterandAuthor Commented:
This is actually the right answer that I wanted. But I think I am gonna put everyone on the same domain. Be less confusion all around. Thanks for the advice!
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now