Windows Server 2003 loses domain membership in NT domain...

I have a windows server 2003 stand alone server that is
joined to an NT 4 domain.

This server supplies the users home directory and the
public drive.

After an hour or so, the server loses its domain
membership and drops out of the domain.

This causes the users home and public drive not to map.

DNS and WINS are working fine on this server and I am
able to ping the domain controller.

I have created an LMHosts file with the following entries:

165.237.107.149 GBOCBNT11 #PRE #DOM:GBO_SYSTEM
165.237.107.149 "GBO_SYSTEM \0x1b" #PRE

I am hoping this will solve the problem.

Does anyone have any ideas about this issue?

I went on Windows Update and all the critical patches
have already been applied. I did notice a driver on
windows update for the integrated NIC card on the server
and installed that. It still loses connection to the
domain controller....

I am running 2003 on a Compaq/HP Proliant DL 380 G3.


>-----Original Message-----
>I have a windows server 2003 stand alone server that is
>joined to an NT 4 domain.
>
>This server supplies the users home directory and the
>public drive.
>
>After an hour or so, the server loses its domain
>membership and drops out of the domain.
>
>This causes the users home and public drive not to map.
>
>DNS and WINS are working fine on this server and I am
>able to ping the domain controller.
>
>I have created an LMHosts file with the following
entries:
>
>165.237.107.149 GBOCBNT11 #PRE #DOM:GBO_SYSTEM
>165.237.107.149 "GBO_SYSTEM \0x1b" #PRE
>
>I am hoping this will solve the problem.
>
>Does anyone have any ideas about this issue?
>.
>

If you go to the WINS tab on TCP/IP properties, is NetBIOS over TCP/IP
enabled?

"Paul Konchar" <(E-Mail Removed)> wrote in message
news:1b4001c50de0$7b443470$(E-Mail Removed)...
>I have a windows server 2003 stand alone server that is
> joined to an NT 4 domain.
>
> This server supplies the users home directory and the
> public drive.
>
> After an hour or so, the server loses its domain
> membership and drops out of the domain.
>
> This causes the users home and public drive not to map.
>
> DNS and WINS are working fine on this server and I am
> able to ping the domain controller.
>
> I have created an LMHosts file with the following entries:
>
> 165.237.107.149 GBOCBNT11 #PRE #DOM:GBO_SYSTEM
> 165.237.107.149 "GBO_SYSTEM \0x1b" #PRE
>
> I am hoping this will solve the problem.
>
> Does anyone have any ideas about this issue?

No, it is set to default: Use NetBios setting from DHCP
server...........

I did, however, notice this error in the System Event
Log....

***********************************************

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 9/6/2004
Time: 9:29:08 PM
User: N/A
Computer: GBOFS01
Description:
This computer was not able to set up a secure session
with a domain controller in domain GBO_SYSTEM due to the
following:
There are currently no logon servers available to service
the logon request.
This may lead to authentication problems. Make sure that
this computer is connected to the network. If the problem
persists, please contact your domain administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified
domain, it sets up the secure session to the primary
domain controller emulator in the specified domain.
Otherwise, this computer sets up the secure session to
any domain controller in the specified domain.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À

*************************************************


We have several other servers that are 2003 on the same
VLAN and same subnet that are not having this problem....



>-----Original Message-----
>If you go to the WINS tab on TCP/IP properties, is
NetBIOS over TCP/IP
>enabled?
>
>"Paul Konchar" <(E-Mail Removed)> wrote in message
>news:1b4001c50de0$7b443470$(E-Mail Removed)...
>>I have a windows server 2003 stand alone server that is
>> joined to an NT 4 domain.
>>
>> This server supplies the users home directory and the
>> public drive.
>>
>> After an hour or so, the server loses its domain
>> membership and drops out of the domain.
>>
>> This causes the users home and public drive not to map.
>>
>> DNS and WINS are working fine on this server and I am
>> able to ping the domain controller.
>>
>> I have created an LMHosts file with the following
entries:
>>
>> 165.237.107.149 GBOCBNT11 #PRE #DOM:GBO_SYSTEM
>> 165.237.107.149 "GBO_SYSTEM \0x1b" #PRE
>>
>> I am hoping this will solve the problem.
>>
>> Does anyone have any ideas about this issue?
>
>
>.
>

Windows 2003 Server has much more secure default settings than NT4.0 and
other downlevel operating systems. More than likely the problem is a
security option. You can access Local Security Policy on the W2003 via
secpol.msc and go to security settings/local policies/security options. At
minimum find the two options for digitally sing communications (always) and
set them to disabled. Then review the KB article below for other potential
compatibility problems. --- Steve

http://support.microsoft.com/default...b;en-us;823659

"Paul Konchar" <(E-Mail Removed)> wrote in message
news:1b4001c50de0$7b443470$(E-Mail Removed)...
>I have a windows server 2003 stand alone server that is
> joined to an NT 4 domain.
>
> This server supplies the users home directory and the
> public drive.
>
> After an hour or so, the server loses its domain
> membership and drops out of the domain.
>
> This causes the users home and public drive not to map.
>
> DNS and WINS are working fine on this server and I am
> able to ping the domain controller.
>
> I have created an LMHosts file with the following entries:
>
> 165.237.107.149 GBOCBNT11 #PRE #DOM:GBO_SYSTEM
> 165.237.107.149 "GBO_SYSTEM \0x1b" #PRE
>
> I am hoping this will solve the problem.
>
> Does anyone have any ideas about this issue?