WIN2003 Server added to NT 4.0 Domain

Is there anything special that you have to do with Active
Directory? I have a similar situation as others. The
existing domain is an NT 4.0 Server with WINXP, WIN2K and
WIN98 clients accessing. I am adding a new server WIN2003
to this domain. I do not have Active Directory running as
yet. I can talk from WIN2003 Server and WIN NT 4.0 Server
but the clients cannot access the WIN2003 Server. Any
ideas?

What's ironic is that the WIN2003 Server is functioning as
the DHCP / DNS and WINS server for the DOmain.


Please advise...

Not sure what you mean by 'the clients cannot access the WIN2003 Server.'
Remember the default share and NTFS permissions are different on Win2003.
You may simply have to add users/groups to your share/NTFS permissions and
possibly Local Security Policy/User Rights Assignment inorder to give
clients access.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"(E-Mail Removed)" <(E-Mail Removed)> wrote in
message news:532701c3b2ad$138649c0$(E-Mail Removed)...
> Is there anything special that you have to do with Active
> Directory? I have a similar situation as others. The
> existing domain is an NT 4.0 Server with WINXP, WIN2K and
> WIN98 clients accessing. I am adding a new server WIN2003
> to this domain. I do not have Active Directory running as
> yet. I can talk from WIN2003 Server and WIN NT 4.0 Server
> but the clients cannot access the WIN2003 Server. Any
> ideas?
>
> What's ironic is that the WIN2003 Server is functioning as
> the DHCP / DNS and WINS server for the DOmain.
>
>
> Please advise...
>
>

Doug,

I have added each user to this WIN2003 Server.
These are some of the messages I get...

-----------------------------------------------------------
\\servername is not accessible. You might not have
permission to use this network resource. Contact the
administrator of this server to find out if you have
access permissions.

The trust relationship between this workstation and the
primary domain failed.
-----------------------------------------------------------


>-----Original Message-----
>Not sure what you mean by 'the clients cannot access the
WIN2003 Server.'
>Remember the default share and NTFS permissions are
different on Win2003.
>You may simply have to add users/groups to your
share/NTFS permissions and
>possibly Local Security Policy/User Rights Assignment
inorder to give
>clients access.
>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
>"(E-Mail Removed)"
<(E-Mail Removed)> wrote in
>message news:532701c3b2ad$138649c0$(E-Mail Removed)...
>> Is there anything special that you have to do with
Active
>> Directory? I have a similar situation as others. The
>> existing domain is an NT 4.0 Server with WINXP, WIN2K
and
>> WIN98 clients accessing. I am adding a new server
WIN2003
>> to this domain. I do not have Active Directory running
as
>> yet. I can talk from WIN2003 Server and WIN NT 4.0
Server
>> but the clients cannot access the WIN2003 Server. Any
>> ideas?
>>
>> What's ironic is that the WIN2003 Server is functioning
as
>> the DHCP / DNS and WINS server for the DOmain.
>>
>>
>> Please advise...
>>
>>
>
>
>.
>

On Mon, 24 Nov 2003 09:04:52 -0800, "(E-Mail Removed)"
<(E-Mail Removed)> wrote:

>Is there anything special that you have to do with Active
>Directory? I have a similar situation as others. The
>existing domain is an NT 4.0 Server with WINXP, WIN2K and
>WIN98 clients accessing. I am adding a new server WIN2003
>to this domain. I do not have Active Directory running as
>yet. I can talk from WIN2003 Server and WIN NT 4.0 Server
>but the clients cannot access the WIN2003 Server. Any
>ideas?

Define "cannot access" and what you've done to enable access.
Assuming the W2K3 server is a member server in the NT domain, and
you've shared something to access, users in the domain should be able
to access it.

>What's ironic is that the WIN2003 Server is functioning as
>the DHCP / DNS and WINS server for the DOmain.

That works fine. And also shouldn't be an issue unless your DHCP
scope has some issues.

Jeff

On Mon, 24 Nov 2003 13:49:49 -0800, "(E-Mail Removed)"
<(E-Mail Removed)> wrote:

>I have added each user to this WIN2003 Server.

As l,ong as the Win2003 server is a member of the NT domain and the
users have domain accounts, you shouldn't be adding users to the
Server 2003 system.

>These are some of the messages I get...
>
>-----------------------------------------------------------
>\\servername is not accessible. You might not have
>permission to use this network resource. Contact the
>administrator of this server to find out if you have
>access permissions.
>
>The trust relationship between this workstation and the
>primary domain failed.
>-----------------------------------------------------------

Okay, is the Server 2003 a member of the NT domain? If not, why not?
And if not, have you established a trust between the NT domain and the
server 2003 domain?

Jeff

>
>
>>-----Original Message-----
>>Not sure what you mean by 'the clients cannot access the
>WIN2003 Server.'
>>Remember the default share and NTFS permissions are
>different on Win2003.
>>You may simply have to add users/groups to your
>share/NTFS permissions and
>>possibly Local Security Policy/User Rights Assignment
>inorder to give
>>clients access.
>>
>>Doug Sherman
>>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>>
>>"(E-Mail Removed)"
><(E-Mail Removed)> wrote in
>>message news:532701c3b2ad$138649c0$(E-Mail Removed)...
>>> Is there anything special that you have to do with
>Active
>>> Directory? I have a similar situation as others. The
>>> existing domain is an NT 4.0 Server with WINXP, WIN2K
>and
>>> WIN98 clients accessing. I am adding a new server
>WIN2003
>>> to this domain. I do not have Active Directory running
>as
>>> yet. I can talk from WIN2003 Server and WIN NT 4.0
>Server
>>> but the clients cannot access the WIN2003 Server. Any
>>> ideas?
>>>
>>> What's ironic is that the WIN2003 Server is functioning
>as
>>> the DHCP / DNS and WINS server for the DOmain.
>>>
>>>
>>> Please advise...
>>>
>>>
>>
>>
>>.
>>

Why wouldn't I add users? The NT 4.0 Server will
eventually go away.



>-----Original Message-----
>On Mon, 24 Nov 2003 13:49:49 -
0800, "(E-Mail Removed)"
><(E-Mail Removed)> wrote:
>
>>I have added each user to this WIN2003 Server.
>
>As l,ong as the Win2003 server is a member of the NT
domain and the
>users have domain accounts, you shouldn't be adding users
to the
>Server 2003 system.
>
>>These are some of the messages I get...
>>
>>---------------------------------------------------------
--
>>\\servername is not accessible. You might not have
>>permission to use this network resource. Contact the
>>administrator of this server to find out if you have
>>access permissions.
>>
>>The trust relationship between this workstation and the
>>primary domain failed.
>>---------------------------------------------------------
--
>
>Okay, is the Server 2003 a member of the NT domain? If
not, why not?
>And if not, have you established a trust between the NT
domain and the
>server 2003 domain?
>
>Jeff
>
>>
>>
>>>-----Original Message-----
>>>Not sure what you mean by 'the clients cannot access
the
>>WIN2003 Server.'
>>>Remember the default share and NTFS permissions are
>>different on Win2003.
>>>You may simply have to add users/groups to your
>>share/NTFS permissions and
>>>possibly Local Security Policy/User Rights Assignment
>>inorder to give
>>>clients access.
>>>
>>>Doug Sherman
>>>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>>>
>>>"(E-Mail Removed)"
>><(E-Mail Removed)> wrote in
>>>message news:532701c3b2ad$138649c0$(E-Mail Removed)...
>>>> Is there anything special that you have to do with
>>Active
>>>> Directory? I have a similar situation as others. The
>>>> existing domain is an NT 4.0 Server with WINXP, WIN2K
>>and
>>>> WIN98 clients accessing. I am adding a new server
>>WIN2003
>>>> to this domain. I do not have Active Directory
running
>>as
>>>> yet. I can talk from WIN2003 Server and WIN NT 4.0
>>Server
>>>> but the clients cannot access the WIN2003 Server. Any
>>>> ideas?
>>>>
>>>> What's ironic is that the WIN2003 Server is
functioning
>>as
>>>> the DHCP / DNS and WINS server for the DOmain.
>>>>
>>>>
>>>> Please advise...
>>>>
>>>>
>>>
>>>
>>>.
>>>
>
>.
>