Server 2003 DC Connectivity Problems!

Hello we have three HP Servers, 1 DC, 1 Exchange & 1 ISA server. In the last
couple of days the DC server has become inaccessible to the network and the
only way to restore connectivity is by reboot but this is happening around 30
mins to an hour after every reboot. When the server looses connectivity i
notice that under compute name its says " The identification of the computer
cannot be changed because networking is not installed or is not properly
configured" - i have reinstalled the network drivers and updated them with
no success but have noticed that when the problem occurs if i remove the
network cable to system still says conected and the properties for the
network card dont change. Group policy object editor also becomes
inaccessable at the time its down! any help would be greaty appreciated.

Hello Lee,

Are all services running? Did you change anything before it starts? Check
on the NIC, that "client for microsoft networks" and "file and printer sharing
for microsoft networks" is installed

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello we have three HP Servers, 1 DC, 1 Exchange & 1 ISA server. In
> the last couple of days the DC server has become inaccessible to the
> network and the only way to restore connectivity is by reboot but this
> is happening around 30 mins to an hour after every reboot. When the
> server looses connectivity i notice that under compute name its says "
> The identification of the computer cannot be changed because
> networking is not installed or is not properly configured" - i have
> reinstalled the network drivers and updated them with no success but
> have noticed that when the problem occurs if i remove the network
> cable to system still says conected and the properties for the network
> card dont change. Group policy object editor also becomes
> inaccessable at the time its down! any help would be greaty
> appreciated.
>

Hello when this went down again i looked at services and found Computer
Browser had stopped, when i restarted it the message gegarding changing
network name went away but still had connectivity issues with computers

"Meinolf Weber [MVP-DS]" wrote:

> Hello Lee,
>
> Are all services running? Did you change anything before it starts? Check
> on the NIC, that "client for microsoft networks" and "file and printer sharing
> for microsoft networks" is installed
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hello we have three HP Servers, 1 DC, 1 Exchange & 1 ISA server. In
> > the last couple of days the DC server has become inaccessible to the
> > network and the only way to restore connectivity is by reboot but this
> > is happening around 30 mins to an hour after every reboot. When the
> > server looses connectivity i notice that under compute name its says "
> > The identification of the computer cannot be changed because
> > networking is not installed or is not properly configured" - i have
> > reinstalled the network drivers and updated them with no success but
> > have noticed that when the problem occurs if i remove the network
> > cable to system still says conected and the properties for the network
> > card dont change. Group policy object editor also becomes
> > inaccessable at the time its down! any help would be greaty
> > appreciated.
> >
>
>
>