Question Locked

Windows 2003 file server in an NT4.0 domain

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I just started this job and it appears that the guy before me installed a windows 2003 server as a file server in an old NT4.0 domain they have here which is on a separate network. There are about 25 XP (sp2) workstations connected to this NT4.0 domain and about 15 additional XP boxes in a workgroup on the same network. I can browse all the workgroup and domain PCs from win2003 box, but I cannot access the win2003 server from any of the 25 client machines on the domain or the workgroup. The message I get is "path was not found, either check permissions..." What can be the issue? This win2003 is a simple file server and not hosting anything. Thank you for your help!

4 replies

by cg it

well if the W2003 server is a member server of the NT domain, then its just the same as any other client on the domain. A folder has to be shared and permissions set for users in the domain to access it. Also, NT domains aren't the same as W2K AD domains. In an NT environment, domains typically were used like security groups, where functional departments were seperated by domains and user accounts were put into whatever domain their functional department belonged to.

A workgroup computer will not be able to access any domain computers because it's not a member of the NT domain[s]. The user account on the workgroup computer also isn't a member of the NT domain[s]. you can allow remote access of workgroup computers granting the user remote access rights but that's about it.

also, W2003 server comes with 5 CALs built in, either device or user, you choose. After the 5 CALs are used up, the server will not accept any more connections. So, for your 25 XPs in the domain environment, your gonna need 20 more CALs. for the workgroup you'll need 15 more CALs. add em up if you want all of em to connect.

by howithink

Thank you for everyone that replied. I figured out what the issue was. In Windows 2003, I had to go into firewall and under exceptions, check mark 'Allow file and print sharing'. So in essence, W2003 firewall was blocking all traffic.

This discussion is closed to new replies.