Problems on Server 2008 Std

Hi

I have got some problems on two of my Windows 2008 servers.
Hardware: both are HP DL380 G5 with newest Firm- and Software.
Running Windows Server 2008 (full patched), AD, DC, DNS Server,
File- and Printserver, Trend Micro Virus Scanner.

Once a week, it seems that the network connections brakes down, although
users still can access shares, etc. Only printing is not possible. The
Symbol of the Trend Micro client looks like a broken
network connection.
I get different error messages in the eventlog like:
Error working group policy object. Name of the DC not found. (...I just
have the German version of the error messages!)
PrintSpooler: ...DNS name couldn't be retrieved!
and so on.

Only rebooting the server solves the problem.

Any ideas?


Thank you very much for your help.

 

Hello Peter,

Sounds like DNS, please post an unedited ipconfig /all from the server. The
DC should not be multihomed, 2 NIC's with different ip addresses. One domain
interal used and one to the ISP's DNS server for example.

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


> Hi
>
> I have got some problems on two of my Windows 2008 servers. Hardware:
> both are HP DL380 G5 with newest Firm- and Software. Running Windows
> Server 2008 (full patched), AD, DC, DNS Server, File- and Printserver,
> Trend Micro Virus Scanner.
>
> Once a week, it seems that the network connections brakes down,
> although
> users still can access shares, etc. Only printing is not possible. The
> Symbol of the Trend Micro client looks like a broken
> network connection.
> I get different error messages in the eventlog like:
> Error working group policy object. Name of the DC not found. (...I
> just
> have the German version of the error messages!)
> PrintSpooler: ...DNS name couldn't be retrieved!
> and so on.
> Only rebooting the server solves the problem.
>
> Any ideas?
>
> Thank you very much for your help.
>

 

There is just one NIC active, the other one was deactivated.
The NIC has two internal IP adresses.

ipconfig /all:

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : SRVINNMAINII
Prim„res DNS-Suffix . . . . . . . : domain.int
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : domain.int

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : HP NC373i Multifunction Gigabit
Server Adapter
Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . :
fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.146.1
DNS-Server . . . . . . . . . . . : ::1
192.168.146.52
192.168.140.66
127.0.0.1
NetBIOS ber TCP/IP . . . . . . . : Aktiviert

Tunneladapter LAN-Verbindung*:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja




Meinolf Weber [MVP-DS] schrieb:
> Hello Peter,
>
> Sounds like DNS, please post an unedited ipconfig /all from the server.
> The DC should not be multihomed, 2 NIC's with different ip addresses.
> One domain interal used and one to the ISP's DNS server for example.
>
> 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
>
>> Hi
>>
>> I have got some problems on two of my Windows 2008 servers. Hardware:
>> both are HP DL380 G5 with newest Firm- and Software. Running Windows
>> Server 2008 (full patched), AD, DC, DNS Server, File- and Printserver,
>> Trend Micro Virus Scanner.
>>
>> Once a week, it seems that the network connections brakes down,
>> although
>> users still can access shares, etc. Only printing is not possible. The
>> Symbol of the Trend Micro client looks like a broken
>> network connection.
>> I get different error messages in the eventlog like:
>> Error working group policy object. Name of the DC not found. (...I
>> just
>> have the German version of the error messages!)
>> PrintSpooler: ...DNS name couldn't be retrieved!
>> and so on.
>> Only rebooting the server solves the problem.
>>
>> Any ideas?
>>
>> Thank you very much for your help.
>>
>
>

 

Hello Peter,

Two different ip's on a DC will create your problems, remove one and it reboot
the netlogon service on the DC. Why did you configure a second ip? Additional
remove the loopback ip 127.0.0.1 from the DNS servers.

What is the DNS server 192.168.140.66 from another subnet?

Also if you not use IPv6 disable it's functionality according to this article:
http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx

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


> There is just one NIC active, the other one was deactivated. The NIC
> has two internal IP adresses.
>
> ipconfig /all:
>
> Windows-IP-Konfiguration
>
> Hostname . . . . . . . . . . . . : SRVINNMAINII
> Prim"res DNS-Suffix . . . . . . . : domain.int
> Knotentyp . . . . . . . . . . . . : Hybrid
> IP-Routing aktiviert . . . . . . : Nein
> WINS-Proxy aktiviert . . . . . . : Nein
> DNS-Suffixsuchliste . . . . . . . : domain.int
> Ethernet-Adapter LAN-Verbindung:
>
> Verbindungsspezifisches DNS-Suffix:
> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
> Gigabit
> Server Adapter
> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
> DHCP aktiviert. . . . . . . . . . : Nein
> Autokonfiguration aktiviert . . . : Ja
> Verbindungslokale IPv6-Adresse . :
> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
> Subnetzmaske . . . . . . . . . . : 255.255.255.0
> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
> Subnetzmaske . . . . . . . . . . : 255.255.255.0
> Standardgateway . . . . . . . . . : 192.168.146.1
> DNS-Server . . . . . . . . . . . : ::1
> 192.168.146.52
> 192.168.140.66
> 127.0.0.1
> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
> Tunneladapter LAN-Verbindung*:
>
> Medienstatus. . . . . . . . . . . : Medium getrennt
> Verbindungsspezifisches DNS-Suffix:
> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP aktiviert. . . . . . . . . . : Nein
> Autokonfiguration aktiviert . . . : Ja
> Meinolf Weber [MVP-DS] schrieb:
>
>> Hello Peter,
>>
>> Sounds like DNS, please post an unedited ipconfig /all from the
>> server. The DC should not be multihomed, 2 NIC's with different ip
>> addresses. One domain interal used and one to the ISP's DNS server
>> for example.
>>
>> 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
>>> Hi
>>>
>>> I have got some problems on two of my Windows 2008 servers.
>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>> Running Windows Server 2008 (full patched), AD, DC, DNS Server,
>>> File- and Printserver, Trend Micro Virus Scanner.
>>>
>>> Once a week, it seems that the network connections brakes down,
>>> although
>>> users still can access shares, etc. Only printing is not possible.
>>> The
>>> Symbol of the Trend Micro client looks like a broken
>>> network connection.
>>> I get different error messages in the eventlog like:
>>> Error working group policy object. Name of the DC not found. (...I
>>> just
>>> have the German version of the error messages!)
>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>> and so on.
>>> Only rebooting the server solves the problem.
>>> Any ideas?
>>>
>>> Thank you very much for your help.
>>>

 

Hi

My domain contains different subnets.
192.168.140.x
192.168.144.x
192.168.145.x
192.168.146.x
Every local DC is DNS Server for his subnet.
192.168.140.66 is a redundant DNS Server for
all subnets.


I think I need the second IP on each DC because the second
IP was the adress of the old server. (...they are replaced by new ones).


Best regards.
Peter


Meinolf Weber [MVP-DS] schrieb:
> Hello Peter,
>
> Two different ip's on a DC will create your problems, remove one and it
> reboot the netlogon service on the DC. Why did you configure a second
> ip? Additional remove the loopback ip 127.0.0.1 from the DNS servers.
>
> What is the DNS server 192.168.140.66 from another subnet?
>
> Also if you not use IPv6 disable it's functionality according to this
> article:
> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx
>
>
> 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
>
>> There is just one NIC active, the other one was deactivated. The NIC
>> has two internal IP adresses.
>>
>> ipconfig /all:
>>
>> Windows-IP-Konfiguration
>>
>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>> Prim"res DNS-Suffix . . . . . . . : domain.int
>> Knotentyp . . . . . . . . . . . . : Hybrid
>> IP-Routing aktiviert . . . . . . : Nein
>> WINS-Proxy aktiviert . . . . . . : Nein
>> DNS-Suffixsuchliste . . . . . . . : domain.int
>> Ethernet-Adapter LAN-Verbindung:
>>
>> Verbindungsspezifisches DNS-Suffix:
>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>> Gigabit
>> Server Adapter
>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>> DHCP aktiviert. . . . . . . . . . : Nein
>> Autokonfiguration aktiviert . . . : Ja
>> Verbindungslokale IPv6-Adresse . :
>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>> Standardgateway . . . . . . . . . : 192.168.146.1
>> DNS-Server . . . . . . . . . . . : ::1
>> 192.168.146.52
>> 192.168.140.66
>> 127.0.0.1
>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>> Tunneladapter LAN-Verbindung*:
>>
>> Medienstatus. . . . . . . . . . . : Medium getrennt
>> Verbindungsspezifisches DNS-Suffix:
>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>> DHCP aktiviert. . . . . . . . . . : Nein
>> Autokonfiguration aktiviert . . . : Ja
>> Meinolf Weber [MVP-DS] schrieb:
>>
>>> Hello Peter,
>>>
>>> Sounds like DNS, please post an unedited ipconfig /all from the
>>> server. The DC should not be multihomed, 2 NIC's with different ip
>>> addresses. One domain interal used and one to the ISP's DNS server
>>> for example.
>>>
>>> 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
>>>> Hi
>>>>
>>>> I have got some problems on two of my Windows 2008 servers.
>>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>>> Running Windows Server 2008 (full patched), AD, DC, DNS Server,
>>>> File- and Printserver, Trend Micro Virus Scanner.
>>>>
>>>> Once a week, it seems that the network connections brakes down,
>>>> although
>>>> users still can access shares, etc. Only printing is not possible.
>>>> The
>>>> Symbol of the Trend Micro client looks like a broken
>>>> network connection.
>>>> I get different error messages in the eventlog like:
>>>> Error working group policy object. Name of the DC not found. (...I
>>>> just
>>>> have the German version of the error messages!)
>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>> and so on.
>>>> Only rebooting the server solves the problem.
>>>> Any ideas?
>>>>
>>>> Thank you very much for your help.
>>>>
>
>

 

Hello Peter,

If the old DC is removed correct from the domain with demoting there shouldn't
be any service running what is using that ip address. REMOVE that ip address
from your DC's and the problems will go.

Please describe why you need this old address in detail, this creates your
problems.

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


> Hi
>
> My domain contains different subnets.
> 192.168.140.x
> 192.168.144.x
> 192.168.145.x
> 192.168.146.x
> Every local DC is DNS Server for his subnet.
> 192.168.140.66 is a redundant DNS Server for
> all subnets.
> I think I need the second IP on each DC because the second IP was the
> adress of the old server. (...they are replaced by new ones).
>
> Best regards.
> Peter
> Meinolf Weber [MVP-DS] schrieb:
>
>> Hello Peter,
>>
>> Two different ip's on a DC will create your problems, remove one and
>> it reboot the netlogon service on the DC. Why did you configure a
>> second ip? Additional remove the loopback ip 127.0.0.1 from the DNS
>> servers.
>>
>> What is the DNS server 192.168.140.66 from another subnet?
>>
>> Also if you not use IPv6 disable it's functionality according to this
>> article:
>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabli
>> ng-ipv6-on-windows-2008.aspx
>>
>> 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
>>> There is just one NIC active, the other one was deactivated. The NIC
>>> has two internal IP adresses.
>>>
>>> ipconfig /all:
>>>
>>> Windows-IP-Konfiguration
>>>
>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>> IP-Routing aktiviert . . . . . . : Nein
>>> WINS-Proxy aktiviert . . . . . . : Nein
>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>> Ethernet-Adapter LAN-Verbindung:
>>> Verbindungsspezifisches DNS-Suffix:
>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>> Gigabit
>>> Server Adapter
>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>> DHCP aktiviert. . . . . . . . . . : Nein
>>> Autokonfiguration aktiviert . . . : Ja
>>> Verbindungslokale IPv6-Adresse . :
>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>> DNS-Server . . . . . . . . . . . : ::1
>>> 192.168.146.52
>>> 192.168.140.66
>>> 127.0.0.1
>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>> Tunneladapter LAN-Verbindung*:
>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>> Verbindungsspezifisches DNS-Suffix:
>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>> DHCP aktiviert. . . . . . . . . . : Nein
>>> Autokonfiguration aktiviert . . . : Ja
>>> Meinolf Weber [MVP-DS] schrieb:
>>>> Hello Peter,
>>>>
>>>> Sounds like DNS, please post an unedited ipconfig /all from the
>>>> server. The DC should not be multihomed, 2 NIC's with different ip
>>>> addresses. One domain interal used and one to the ISP's DNS server
>>>> for example.
>>>>
>>>> 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
>>>>> Hi
>>>>>
>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>>>> Running Windows Server 2008 (full patched), AD, DC, DNS Server,
>>>>> File- and Printserver, Trend Micro Virus Scanner.
>>>>>
>>>>> Once a week, it seems that the network connections brakes down,
>>>>> although
>>>>> users still can access shares, etc. Only printing is not possible.
>>>>> The
>>>>> Symbol of the Trend Micro client looks like a broken
>>>>> network connection.
>>>>> I get different error messages in the eventlog like:
>>>>> Error working group policy object. Name of the DC not found. (...I
>>>>> just
>>>>> have the German version of the error messages!)
>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>> and so on.
>>>>> Only rebooting the server solves the problem.
>>>>> Any ideas?
>>>>> Thank you very much for your help.
>>>>>

 

Hi

We have some software (not standard software) which have some
"hardcoded" links with the "old" ip adress. That's why I need the
old adress. But I'll try to remove it.

What about DNS, is it ok, that I use the DC (192.168.140.66) from
another subnet as secondary DNS server?

Best Regards.


Meinolf Weber [MVP-DS] schrieb:
> Hello Peter,
>
> If the old DC is removed correct from the domain with demoting there
> shouldn't be any service running what is using that ip address. REMOVE
> that ip address from your DC's and the problems will go.
>
> Please describe why you need this old address in detail, this creates
> your problems.
>
> 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
>
>> Hi
>>
>> My domain contains different subnets.
>> 192.168.140.x
>> 192.168.144.x
>> 192.168.145.x
>> 192.168.146.x
>> Every local DC is DNS Server for his subnet.
>> 192.168.140.66 is a redundant DNS Server for
>> all subnets.
>> I think I need the second IP on each DC because the second IP was the
>> adress of the old server. (...they are replaced by new ones).
>>
>> Best regards.
>> Peter
>> Meinolf Weber [MVP-DS] schrieb:
>>
>>> Hello Peter,
>>>
>>> Two different ip's on a DC will create your problems, remove one and
>>> it reboot the netlogon service on the DC. Why did you configure a
>>> second ip? Additional remove the loopback ip 127.0.0.1 from the DNS
>>> servers.
>>>
>>> What is the DNS server 192.168.140.66 from another subnet?
>>>
>>> Also if you not use IPv6 disable it's functionality according to this
>>> article:
>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabli
>>> ng-ipv6-on-windows-2008.aspx
>>>
>>> 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
>>>> There is just one NIC active, the other one was deactivated. The NIC
>>>> has two internal IP adresses.
>>>>
>>>> ipconfig /all:
>>>>
>>>> Windows-IP-Konfiguration
>>>>
>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>> IP-Routing aktiviert . . . . . . : Nein
>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>> Ethernet-Adapter LAN-Verbindung:
>>>> Verbindungsspezifisches DNS-Suffix:
>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>> Gigabit
>>>> Server Adapter
>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>> Autokonfiguration aktiviert . . . : Ja
>>>> Verbindungslokale IPv6-Adresse . :
>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>> DNS-Server . . . . . . . . . . . : ::1
>>>> 192.168.146.52
>>>> 192.168.140.66
>>>> 127.0.0.1
>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>> Tunneladapter LAN-Verbindung*:
>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>> Verbindungsspezifisches DNS-Suffix:
>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>> Autokonfiguration aktiviert . . . : Ja
>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>> Hello Peter,
>>>>>
>>>>> Sounds like DNS, please post an unedited ipconfig /all from the
>>>>> server. The DC should not be multihomed, 2 NIC's with different ip
>>>>> addresses. One domain interal used and one to the ISP's DNS server
>>>>> for example.
>>>>>
>>>>> 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
>>>>>> Hi
>>>>>>
>>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>>>>> Running Windows Server 2008 (full patched), AD, DC, DNS Server,
>>>>>> File- and Printserver, Trend Micro Virus Scanner.
>>>>>>
>>>>>> Once a week, it seems that the network connections brakes down,
>>>>>> although
>>>>>> users still can access shares, etc. Only printing is not possible.
>>>>>> The
>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>> network connection.
>>>>>> I get different error messages in the eventlog like:
>>>>>> Error working group policy object. Name of the DC not found. (...I
>>>>>> just
>>>>>> have the German version of the error messages!)
>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>> and so on.
>>>>>> Only rebooting the server solves the problem.
>>>>>> Any ideas?
>>>>>> Thank you very much for your help.
>>>>>>
>
>

 

Hello Peter,

If the software is written that badly , you should get the programmer to
fix that. If the ip is needed why not using one of the available DNS servers
and change the ip address to the old one, assuming that DNS is the reason
for the old ip?

A DNS server from another subnet as secondary is ok.

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


> Hi
>
> We have some software (not standard software) which have some
> "hardcoded" links with the "old" ip adress. That's why I need the old
> adress. But I'll try to remove it.
>
> What about DNS, is it ok, that I use the DC (192.168.140.66) from
> another subnet as secondary DNS server?
>
> Best Regards.
>
> Meinolf Weber [MVP-DS] schrieb:
>
>> Hello Peter,
>>
>> If the old DC is removed correct from the domain with demoting there
>> shouldn't be any service running what is using that ip address.
>> REMOVE that ip address from your DC's and the problems will go.
>>
>> Please describe why you need this old address in detail, this creates
>> your problems.
>>
>> 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
>>> Hi
>>>
>>> My domain contains different subnets.
>>> 192.168.140.x
>>> 192.168.144.x
>>> 192.168.145.x
>>> 192.168.146.x
>>> Every local DC is DNS Server for his subnet.
>>> 192.168.140.66 is a redundant DNS Server for
>>> all subnets.
>>> I think I need the second IP on each DC because the second IP was
>>> the
>>> adress of the old server. (...they are replaced by new ones).
>>> Best regards.
>>> Peter
>>> Meinolf Weber [MVP-DS] schrieb:
>>>> Hello Peter,
>>>>
>>>> Two different ip's on a DC will create your problems, remove one
>>>> and it reboot the netlogon service on the DC. Why did you configure
>>>> a second ip? Additional remove the loopback ip 127.0.0.1 from the
>>>> DNS servers.
>>>>
>>>> What is the DNS server 192.168.140.66 from another subnet?
>>>>
>>>> Also if you not use IPv6 disable it's functionality according to
>>>> this article:
>>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disab
>>>> li ng-ipv6-on-windows-2008.aspx
>>>>
>>>> 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
>>>>> There is just one NIC active, the other one was deactivated. The
>>>>> NIC has two internal IP adresses.
>>>>>
>>>>> ipconfig /all:
>>>>>
>>>>> Windows-IP-Konfiguration
>>>>>
>>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>>> IP-Routing aktiviert . . . . . . : Nein
>>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>>> Ethernet-Adapter LAN-Verbindung:
>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>>> Gigabit
>>>>> Server Adapter
>>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>> Verbindungslokale IPv6-Adresse . :
>>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>>> DNS-Server . . . . . . . . . . . : ::1
>>>>> 192.168.146.52
>>>>> 192.168.140.66
>>>>> 127.0.0.1
>>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>> Tunneladapter LAN-Verbindung*:
>>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>> Hello Peter,
>>>>>>
>>>>>> Sounds like DNS, please post an unedited ipconfig /all from the
>>>>>> server. The DC should not be multihomed, 2 NIC's with different
>>>>>> ip addresses. One domain interal used and one to the ISP's DNS
>>>>>> server for example.
>>>>>>
>>>>>> 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
>>>>>>> Hi
>>>>>>>
>>>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>>>>>> Running Windows Server 2008 (full patched), AD, DC, DNS Server,
>>>>>>> File- and Printserver, Trend Micro Virus Scanner.
>>>>>>>
>>>>>>> Once a week, it seems that the network connections brakes down,
>>>>>>> although
>>>>>>> users still can access shares, etc. Only printing is not
>>>>>>> possible.
>>>>>>> The
>>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>>> network connection.
>>>>>>> I get different error messages in the eventlog like:
>>>>>>> Error working group policy object. Name of the DC not found.
>>>>>>> (...I
>>>>>>> just
>>>>>>> have the German version of the error messages!)
>>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>>> and so on.
>>>>>>> Only rebooting the server solves the problem.
>>>>>>> Any ideas?
>>>>>>> Thank you very much for your help.

 

I got the same error's again today.
Any suggestions what I can still do?

Best Regards.
Peter


Meinolf Weber [MVP-DS] schrieb:
> Hello Peter,
>
> If the software is written that badly , you should get the programmer to
> fix that. If the ip is needed why not using one of the available DNS
> servers and change the ip address to the old one, assuming that DNS is
> the reason for the old ip?
>
> A DNS server from another subnet as secondary is ok.
>
> 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
>
>> Hi
>>
>> We have some software (not standard software) which have some
>> "hardcoded" links with the "old" ip adress. That's why I need the old
>> adress. But I'll try to remove it.
>>
>> What about DNS, is it ok, that I use the DC (192.168.140.66) from
>> another subnet as secondary DNS server?
>>
>> Best Regards.
>>
>> Meinolf Weber [MVP-DS] schrieb:
>>
>>> Hello Peter,
>>>
>>> If the old DC is removed correct from the domain with demoting there
>>> shouldn't be any service running what is using that ip address.
>>> REMOVE that ip address from your DC's and the problems will go.
>>>
>>> Please describe why you need this old address in detail, this creates
>>> your problems.
>>>
>>> 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
>>>> Hi
>>>>
>>>> My domain contains different subnets.
>>>> 192.168.140.x
>>>> 192.168.144.x
>>>> 192.168.145.x
>>>> 192.168.146.x
>>>> Every local DC is DNS Server for his subnet.
>>>> 192.168.140.66 is a redundant DNS Server for
>>>> all subnets.
>>>> I think I need the second IP on each DC because the second IP was
>>>> the
>>>> adress of the old server. (...they are replaced by new ones).
>>>> Best regards.
>>>> Peter
>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>> Hello Peter,
>>>>>
>>>>> Two different ip's on a DC will create your problems, remove one
>>>>> and it reboot the netlogon service on the DC. Why did you configure
>>>>> a second ip? Additional remove the loopback ip 127.0.0.1 from the
>>>>> DNS servers.
>>>>>
>>>>> What is the DNS server 192.168.140.66 from another subnet?
>>>>>
>>>>> Also if you not use IPv6 disable it's functionality according to
>>>>> this article:
>>>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disab
>>>>> li ng-ipv6-on-windows-2008.aspx
>>>>>
>>>>> 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
>>>>>> There is just one NIC active, the other one was deactivated. The
>>>>>> NIC has two internal IP adresses.
>>>>>>
>>>>>> ipconfig /all:
>>>>>>
>>>>>> Windows-IP-Konfiguration
>>>>>>
>>>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>>>> IP-Routing aktiviert . . . . . . : Nein
>>>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>>>> Ethernet-Adapter LAN-Verbindung:
>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>>>> Gigabit
>>>>>> Server Adapter
>>>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>> Verbindungslokale IPv6-Adresse . :
>>>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>>>> DNS-Server . . . . . . . . . . . : ::1
>>>>>> 192.168.146.52
>>>>>> 192.168.140.66
>>>>>> 127.0.0.1
>>>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>>> Tunneladapter LAN-Verbindung*:
>>>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>> Hello Peter,
>>>>>>>
>>>>>>> Sounds like DNS, please post an unedited ipconfig /all from the
>>>>>>> server. The DC should not be multihomed, 2 NIC's with different
>>>>>>> ip addresses. One domain interal used and one to the ISP's DNS
>>>>>>> server for example.
>>>>>>>
>>>>>>> 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
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>>>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>>>>>>> Running Windows Server 2008 (full patched), AD, DC, DNS Server,
>>>>>>>> File- and Printserver, Trend Micro Virus Scanner.
>>>>>>>>
>>>>>>>> Once a week, it seems that the network connections brakes down,
>>>>>>>> although
>>>>>>>> users still can access shares, etc. Only printing is not
>>>>>>>> possible.
>>>>>>>> The
>>>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>>>> network connection.
>>>>>>>> I get different error messages in the eventlog like:
>>>>>>>> Error working group policy object. Name of the DC not found.
>>>>>>>> (...I
>>>>>>>> just
>>>>>>>> have the German version of the error messages!)
>>>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>>>> and so on.
>>>>>>>> Only rebooting the server solves the problem.
>>>>>>>> Any ideas?
>>>>>>>> Thank you very much for your help.
>
>

 

Hello Peter,

See the suggestion in my previous posting.

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


> I got the same error's again today.
> Any suggestions what I can still do?
> Best Regards.
> Peter
> Meinolf Weber [MVP-DS] schrieb:
>
>> Hello Peter,
>>
>> If the software is written that badly , you should get the programmer
>> to fix that. If the ip is needed why not using one of the available
>> DNS servers and change the ip address to the old one, assuming that
>> DNS is the reason for the old ip?
>>
>> A DNS server from another subnet as secondary is ok.
>>
>> 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
>>> Hi
>>>
>>> We have some software (not standard software) which have some
>>> "hardcoded" links with the "old" ip adress. That's why I need the
>>> old adress. But I'll try to remove it.
>>>
>>> What about DNS, is it ok, that I use the DC (192.168.140.66) from
>>> another subnet as secondary DNS server?
>>>
>>> Best Regards.
>>>
>>> Meinolf Weber [MVP-DS] schrieb:
>>>
>>>> Hello Peter,
>>>>
>>>> If the old DC is removed correct from the domain with demoting
>>>> there shouldn't be any service running what is using that ip
>>>> address. REMOVE that ip address from your DC's and the problems
>>>> will go.
>>>>
>>>> Please describe why you need this old address in detail, this
>>>> creates your problems.
>>>>
>>>> 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
>>>>> Hi
>>>>>
>>>>> My domain contains different subnets.
>>>>> 192.168.140.x
>>>>> 192.168.144.x
>>>>> 192.168.145.x
>>>>> 192.168.146.x
>>>>> Every local DC is DNS Server for his subnet.
>>>>> 192.168.140.66 is a redundant DNS Server for
>>>>> all subnets.
>>>>> I think I need the second IP on each DC because the second IP was
>>>>> the
>>>>> adress of the old server. (...they are replaced by new ones).
>>>>> Best regards.
>>>>> Peter
>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>> Hello Peter,
>>>>>>
>>>>>> Two different ip's on a DC will create your problems, remove one
>>>>>> and it reboot the netlogon service on the DC. Why did you
>>>>>> configure a second ip? Additional remove the loopback ip
>>>>>> 127.0.0.1 from the DNS servers.
>>>>>>
>>>>>> What is the DNS server 192.168.140.66 from another subnet?
>>>>>>
>>>>>> Also if you not use IPv6 disable it's functionality according to
>>>>>> this article:
>>>>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/dis
>>>>>> ab li ng-ipv6-on-windows-2008.aspx
>>>>>>
>>>>>> 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
>>>>>>> There is just one NIC active, the other one was deactivated. The
>>>>>>> NIC has two internal IP adresses.
>>>>>>>
>>>>>>> ipconfig /all:
>>>>>>>
>>>>>>> Windows-IP-Konfiguration
>>>>>>>
>>>>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>>>>> IP-Routing aktiviert . . . . . . : Nein
>>>>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>>>>> Ethernet-Adapter LAN-Verbindung:
>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>>>>> Gigabit
>>>>>>> Server Adapter
>>>>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>> Verbindungslokale IPv6-Adresse . :
>>>>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>>>>> DNS-Server . . . . . . . . . . . : ::1
>>>>>>> 192.168.146.52
>>>>>>> 192.168.140.66
>>>>>>> 127.0.0.1
>>>>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>>>> Tunneladapter LAN-Verbindung*:
>>>>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>> Hello Peter,
>>>>>>>>
>>>>>>>> Sounds like DNS, please post an unedited ipconfig /all from the
>>>>>>>> server. The DC should not be multihomed, 2 NIC's with different
>>>>>>>> ip addresses. One domain interal used and one to the ISP's DNS
>>>>>>>> server for example.
>>>>>>>>
>>>>>>>> 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
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>>>>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>>>>>>>> Running Windows Server 2008 (full patched), AD, DC, DNS
>>>>>>>>> Server, File- and Printserver, Trend Micro Virus Scanner.
>>>>>>>>>
>>>>>>>>> Once a week, it seems that the network connections brakes
>>>>>>>>> down,
>>>>>>>>> although
>>>>>>>>> users still can access shares, etc. Only printing is not
>>>>>>>>> possible.
>>>>>>>>> The
>>>>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>>>>> network connection.
>>>>>>>>> I get different error messages in the eventlog like:
>>>>>>>>> Error working group policy object. Name of the DC not found.
>>>>>>>>> (...I
>>>>>>>>> just
>>>>>>>>> have the German version of the error messages!)
>>>>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>>>>> and so on.
>>>>>>>>> Only rebooting the server solves the problem.
>>>>>>>>> Any ideas?
>>>>>>>>> Thank you very much for your help.

 

Hi

I already changed what you suggested, without success.
Today I had the problem on an 2008 Server which worked fine until
this morning. It was the first that, that he "crashed"

Then "something" crashed and I got the errors mentioned
below.
What I found out: It only happend on Windows Server 2008 Std. installed
on brandnew HP ProLiant DL380 G5 and ProLiant DL320G5p.

Best Regards.
Peter




Meinolf Weber [MVP-DS] schrieb:
> Hello Peter,
>
> See the suggestion in my previous posting.
>
> 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
>
>> I got the same error's again today.
>> Any suggestions what I can still do?
>> Best Regards.
>> Peter
>> Meinolf Weber [MVP-DS] schrieb:
>>
>>> Hello Peter,
>>>
>>> If the software is written that badly , you should get the programmer
>>> to fix that. If the ip is needed why not using one of the available
>>> DNS servers and change the ip address to the old one, assuming that
>>> DNS is the reason for the old ip?
>>>
>>> A DNS server from another subnet as secondary is ok.
>>>
>>> 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
>>>> Hi
>>>>
>>>> We have some software (not standard software) which have some
>>>> "hardcoded" links with the "old" ip adress. That's why I need the
>>>> old adress. But I'll try to remove it.
>>>>
>>>> What about DNS, is it ok, that I use the DC (192.168.140.66) from
>>>> another subnet as secondary DNS server?
>>>>
>>>> Best Regards.
>>>>
>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>
>>>>> Hello Peter,
>>>>>
>>>>> If the old DC is removed correct from the domain with demoting
>>>>> there shouldn't be any service running what is using that ip
>>>>> address. REMOVE that ip address from your DC's and the problems
>>>>> will go.
>>>>>
>>>>> Please describe why you need this old address in detail, this
>>>>> creates your problems.
>>>>>
>>>>> 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
>>>>>> Hi
>>>>>>
>>>>>> My domain contains different subnets.
>>>>>> 192.168.140.x
>>>>>> 192.168.144.x
>>>>>> 192.168.145.x
>>>>>> 192.168.146.x
>>>>>> Every local DC is DNS Server for his subnet.
>>>>>> 192.168.140.66 is a redundant DNS Server for
>>>>>> all subnets.
>>>>>> I think I need the second IP on each DC because the second IP was
>>>>>> the
>>>>>> adress of the old server. (...they are replaced by new ones).
>>>>>> Best regards.
>>>>>> Peter
>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>> Hello Peter,
>>>>>>>
>>>>>>> Two different ip's on a DC will create your problems, remove one
>>>>>>> and it reboot the netlogon service on the DC. Why did you
>>>>>>> configure a second ip? Additional remove the loopback ip
>>>>>>> 127.0.0.1 from the DNS servers.
>>>>>>>
>>>>>>> What is the DNS server 192.168.140.66 from another subnet?
>>>>>>>
>>>>>>> Also if you not use IPv6 disable it's functionality according to
>>>>>>> this article:
>>>>>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/dis
>>>>>>> ab li ng-ipv6-on-windows-2008.aspx
>>>>>>>
>>>>>>> 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
>>>>>>>> There is just one NIC active, the other one was deactivated. The
>>>>>>>> NIC has two internal IP adresses.
>>>>>>>>
>>>>>>>> ipconfig /all:
>>>>>>>>
>>>>>>>> Windows-IP-Konfiguration
>>>>>>>>
>>>>>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>>>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>>>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>>>>>> IP-Routing aktiviert . . . . . . : Nein
>>>>>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>>>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>>>>>> Ethernet-Adapter LAN-Verbindung:
>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>>>>>> Gigabit
>>>>>>>> Server Adapter
>>>>>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>> Verbindungslokale IPv6-Adresse . :
>>>>>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>>>>>> DNS-Server . . . . . . . . . . . : ::1
>>>>>>>> 192.168.146.52
>>>>>>>> 192.168.140.66
>>>>>>>> 127.0.0.1
>>>>>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>>>>> Tunneladapter LAN-Verbindung*:
>>>>>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>>>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>>> Hello Peter,
>>>>>>>>>
>>>>>>>>> Sounds like DNS, please post an unedited ipconfig /all from the
>>>>>>>>> server. The DC should not be multihomed, 2 NIC's with different
>>>>>>>>> ip addresses. One domain interal used and one to the ISP's DNS
>>>>>>>>> server for example.
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>>>>>>> Hardware: both are HP DL380 G5 with newest Firm- and Software.
>>>>>>>>>> Running Windows Server 2008 (full patched), AD, DC, DNS
>>>>>>>>>> Server, File- and Printserver, Trend Micro Virus Scanner.
>>>>>>>>>>
>>>>>>>>>> Once a week, it seems that the network connections brakes
>>>>>>>>>> down,
>>>>>>>>>> although
>>>>>>>>>> users still can access shares, etc. Only printing is not
>>>>>>>>>> possible.
>>>>>>>>>> The
>>>>>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>>>>>> network connection.
>>>>>>>>>> I get different error messages in the eventlog like:
>>>>>>>>>> Error working group policy object. Name of the DC not found.
>>>>>>>>>> (...I
>>>>>>>>>> just
>>>>>>>>>> have the German version of the error messages!)
>>>>>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>>>>>> and so on.
>>>>>>>>>> Only rebooting the server solves the problem.
>>>>>>>>>> Any ideas?
>>>>>>>>>> Thank you very much for your help.
>
>

 

Hello Peter,

So it seems that the ip address was not based on DNS? Strange in my opinion,
what does the application request from the servers?

For your error please describe mroe detailed as "crashed", what errors in
the event viewer or on the server, blue screen?

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


> Hi
>
> I already changed what you suggested, without success.
> Today I had the problem on an 2008 Server which worked fine until
> this morning. It was the first that, that he "crashed"
> Then "something" crashed and I got the errors mentioned
> below.
> What I found out: It only happend on Windows Server 2008 Std.
> installed
> on brandnew HP ProLiant DL380 G5 and ProLiant DL320G5p.
> Best Regards.
> Peter
> Meinolf Weber [MVP-DS] schrieb:
>
>> Hello Peter,
>>
>> See the suggestion in my previous posting.
>>
>> 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
>>> I got the same error's again today.
>>> Any suggestions what I can still do?
>>> Best Regards.
>>> Peter
>>> Meinolf Weber [MVP-DS] schrieb:
>>>> Hello Peter,
>>>>
>>>> If the software is written that badly , you should get the
>>>> programmer to fix that. If the ip is needed why not using one of
>>>> the available DNS servers and change the ip address to the old one,
>>>> assuming that DNS is the reason for the old ip?
>>>>
>>>> A DNS server from another subnet as secondary is ok.
>>>>
>>>> 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
>>>>> Hi
>>>>>
>>>>> We have some software (not standard software) which have some
>>>>> "hardcoded" links with the "old" ip adress. That's why I need the
>>>>> old adress. But I'll try to remove it.
>>>>>
>>>>> What about DNS, is it ok, that I use the DC (192.168.140.66) from
>>>>> another subnet as secondary DNS server?
>>>>>
>>>>> Best Regards.
>>>>>
>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>
>>>>>> Hello Peter,
>>>>>>
>>>>>> If the old DC is removed correct from the domain with demoting
>>>>>> there shouldn't be any service running what is using that ip
>>>>>> address. REMOVE that ip address from your DC's and the problems
>>>>>> will go.
>>>>>>
>>>>>> Please describe why you need this old address in detail, this
>>>>>> creates your problems.
>>>>>>
>>>>>> 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
>>>>>>> Hi
>>>>>>>
>>>>>>> My domain contains different subnets.
>>>>>>> 192.168.140.x
>>>>>>> 192.168.144.x
>>>>>>> 192.168.145.x
>>>>>>> 192.168.146.x
>>>>>>> Every local DC is DNS Server for his subnet.
>>>>>>> 192.168.140.66 is a redundant DNS Server for
>>>>>>> all subnets.
>>>>>>> I think I need the second IP on each DC because the second IP
>>>>>>> was
>>>>>>> the
>>>>>>> adress of the old server. (...they are replaced by new ones).
>>>>>>> Best regards.
>>>>>>> Peter
>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>> Hello Peter,
>>>>>>>>
>>>>>>>> Two different ip's on a DC will create your problems, remove
>>>>>>>> one and it reboot the netlogon service on the DC. Why did you
>>>>>>>> configure a second ip? Additional remove the loopback ip
>>>>>>>> 127.0.0.1 from the DNS servers.
>>>>>>>>
>>>>>>>> What is the DNS server 192.168.140.66 from another subnet?
>>>>>>>>
>>>>>>>> Also if you not use IPv6 disable it's functionality according
>>>>>>>> to this article:
>>>>>>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/d
>>>>>>>> is ab li ng-ipv6-on-windows-2008.aspx
>>>>>>>>
>>>>>>>> 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
>>>>>>>>> There is just one NIC active, the other one was deactivated.
>>>>>>>>> The NIC has two internal IP adresses.
>>>>>>>>>
>>>>>>>>> ipconfig /all:
>>>>>>>>>
>>>>>>>>> Windows-IP-Konfiguration
>>>>>>>>>
>>>>>>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>>>>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>>>>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>>>>>>> IP-Routing aktiviert . . . . . . : Nein
>>>>>>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>>>>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>>>>>>> Ethernet-Adapter LAN-Verbindung:
>>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>>>>>>> Gigabit
>>>>>>>>> Server Adapter
>>>>>>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>>> Verbindungslokale IPv6-Adresse . :
>>>>>>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>>>>>>> DNS-Server . . . . . . . . . . . : ::1
>>>>>>>>> 192.168.146.52
>>>>>>>>> 192.168.140.66
>>>>>>>>> 127.0.0.1
>>>>>>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>>>>>> Tunneladapter LAN-Verbindung*:
>>>>>>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>>>>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>>>> Hello Peter,
>>>>>>>>>>
>>>>>>>>>> Sounds like DNS, please post an unedited ipconfig /all from
>>>>>>>>>> the server. The DC should not be multihomed, 2 NIC's with
>>>>>>>>>> different ip addresses. One domain interal used and one to
>>>>>>>>>> the ISP's DNS server for example.
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>>>>>>>> Hardware: both are HP DL380 G5 with newest Firm- and
>>>>>>>>>>> Software. Running Windows Server 2008 (full patched), AD,
>>>>>>>>>>> DC, DNS Server, File- and Printserver, Trend Micro Virus
>>>>>>>>>>> Scanner.
>>>>>>>>>>>
>>>>>>>>>>> Once a week, it seems that the network connections brakes
>>>>>>>>>>> down,
>>>>>>>>>>> although
>>>>>>>>>>> users still can access shares, etc. Only printing is not
>>>>>>>>>>> possible.
>>>>>>>>>>> The
>>>>>>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>>>>>>> network connection.
>>>>>>>>>>> I get different error messages in the eventlog like:
>>>>>>>>>>> Error working group policy object. Name of the DC not found.
>>>>>>>>>>> (...I
>>>>>>>>>>> just
>>>>>>>>>>> have the German version of the error messages!)
>>>>>>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>>>>>>> and so on.
>>>>>>>>>>> Only rebooting the server solves the problem.
>>>>>>>>>>> Any ideas?
>>>>>>>>>>> Thank you very much for your help.

 

Hello

The server which had the problems, is only DC controller and "master
server", that means that he has the FSMO roles.
There is no bluescreen, normally you can't print and can't access
network shares. In my opinion the error's come from the NIC.
Error messages:

Fehler bei der Verarbeitung der Gruppenrichtlinie. Der Name eines
Domänencontrollers konnte nicht abgerufen werden. Dies kann auf einen
Fehler bei der Namensauflösung zurückzuführen sein. Überprüfen Sie, ob
DNS (Domain Name System) konfiguriert ist und richtig ausgeführt wird.

Der DNS-Server konnte ein TCP-Socket nicht an die Adresse 0.0.0.0
binden. Die Ereignisdaten enthalten den Fehlercode. Eine IP-Adresse von
0.0.0.0 bedeutet, dass ein Socket alle verfügbaren IP-Adressen des
Computers verwendet (eine gültige Konfiguration).
Starten Sie den DNS-Server bzw. den Computer neu.

Der DNS-Server konnte den Socket für die Adresse 0.0.0.0 nicht öffnen.
Überprüfen Sie, ob diese IP-Adresse auf dem Servercomputer gültig ist.
Verwenden Sie im DNS-Manager das Eigenschaftenfenster des Servers und
dort die Registerkarte "Schnittstellen", um diese Adresse gegebenenfalls
von der Adressliste zu entfernen. Starten Sie den DNS-Server danach
erneut. (Falls diese Adresse die einzige IP-Schnittstelle auf diesem
Computer war, konnte der DNS-Server wahrscheinlich aufgrund dieses
Fehlers nicht starten. In diesem Fall entfernen Sie den Eintrag
"ListenAddress" in der Registrierung unter "\Services\DNS\Parameters",
und führen Sie einen Neustart durch.)

Wenn diese IP-Adresse auf dem Computer gültig ist, sollten Sie
sicherstellen, dass keine andere Anwendung (z.B. ein anderer DNS-Server)
aktiv ist, die versucht, auf den DNS-Port zuzugreifen.

Weitere Informationen hierzu finden Sie in der Onlinehilfe im Abschnitt
"DNS-Serverprotokollierungsreferenz".

Die Konsistenzprüfung hat Probleme mit der folgenden
Verzeichnispartition festgestellt.

Verzeichnispartition:
DC=ForestDnsZones,DC=domain,DC=int

Es gibt für die Konsistenzprüfung nicht genügend
Standortskonnektivitätsinformationen, um eine umfassende
Gesamtstruktur-Replikationstopologie zu erstellen. Zudem besteht die
Möglichkeit, dass mindestens ein Verzeichnisserver mit dieser
Verzeichnispartition nicht in der Lage war, die
Verzeichnispartitioninformationen zu replizieren. Dies liegt vermutlich
an nicht zugreifbaren Verzeichnisservern.

Benutzeraktion
Führen Sie einen der folgenden Schritte aus:
- Veröffentlichen Sie genügend Informationen über Standortkonnektivität,
sodass die Konsistenzprüfung eine Route ermitteln kann, durch die die
Verzeichnispartition diesen Standort erreichen kann. Diese Option wird
empfohlen.
- Fügen Sie von einem Verzeichnisdienst mit derselben
Verzeichnispartition auf einem anderen Standort ein Verbindungsobjekt zu
einem Verzeichnisdienst mit der Verzeichnispartition an diesem Standort
hinzu.

Wenn keine dieser beiden Tasks den Problemzustand behebt, überprüfen Sie
die bisher durch die Konsistenzprüfung protokollierten Ereignisse, die
die nicht zugreifbaren Verzeichnisserver identifizieren.

Alle Verzeichnisdienste am folgenden Standort, die die
Verzeichnispartition über diesen Transport replizieren können, sind
zurzeit nicht verfügbar.

Standort:
CN=Innsbruck,CN=Sites,CN=Configuration,DC=domain,DC=int
Verzeichnispartition:
CN=Configuration,DC=domain,DC=int
Transport:
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=domain,DC=int

Best regards.
Peter


Meinolf Weber [MVP-DS] schrieb:
> Hello Peter,
>
> So it seems that the ip address was not based on DNS? Strange in my
> opinion, what does the application request from the servers?
>
> For your error please describe mroe detailed as "crashed", what errors
> in the event viewer or on the server, blue screen?
>
> 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
>
>> Hi
>>
>> I already changed what you suggested, without success.
>> Today I had the problem on an 2008 Server which worked fine until
>> this morning. It was the first that, that he "crashed"
>> Then "something" crashed and I got the errors mentioned
>> below.
>> What I found out: It only happend on Windows Server 2008 Std.
>> installed
>> on brandnew HP ProLiant DL380 G5 and ProLiant DL320G5p.
>> Best Regards.
>> Peter
>> Meinolf Weber [MVP-DS] schrieb:
>>
>>> Hello Peter,
>>>
>>> See the suggestion in my previous posting.
>>>
>>> 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
>>>> I got the same error's again today.
>>>> Any suggestions what I can still do?
>>>> Best Regards.
>>>> Peter
>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>> Hello Peter,
>>>>>
>>>>> If the software is written that badly , you should get the
>>>>> programmer to fix that. If the ip is needed why not using one of
>>>>> the available DNS servers and change the ip address to the old one,
>>>>> assuming that DNS is the reason for the old ip?
>>>>>
>>>>> A DNS server from another subnet as secondary is ok.
>>>>>
>>>>> 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
>>>>>> Hi
>>>>>>
>>>>>> We have some software (not standard software) which have some
>>>>>> "hardcoded" links with the "old" ip adress. That's why I need the
>>>>>> old adress. But I'll try to remove it.
>>>>>>
>>>>>> What about DNS, is it ok, that I use the DC (192.168.140.66) from
>>>>>> another subnet as secondary DNS server?
>>>>>>
>>>>>> Best Regards.
>>>>>>
>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>
>>>>>>> Hello Peter,
>>>>>>>
>>>>>>> If the old DC is removed correct from the domain with demoting
>>>>>>> there shouldn't be any service running what is using that ip
>>>>>>> address. REMOVE that ip address from your DC's and the problems
>>>>>>> will go.
>>>>>>>
>>>>>>> Please describe why you need this old address in detail, this
>>>>>>> creates your problems.
>>>>>>>
>>>>>>> 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
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> My domain contains different subnets.
>>>>>>>> 192.168.140.x
>>>>>>>> 192.168.144.x
>>>>>>>> 192.168.145.x
>>>>>>>> 192.168.146.x
>>>>>>>> Every local DC is DNS Server for his subnet.
>>>>>>>> 192.168.140.66 is a redundant DNS Server for
>>>>>>>> all subnets.
>>>>>>>> I think I need the second IP on each DC because the second IP
>>>>>>>> was
>>>>>>>> the
>>>>>>>> adress of the old server. (...they are replaced by new ones).
>>>>>>>> Best regards.
>>>>>>>> Peter
>>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>>> Hello Peter,
>>>>>>>>>
>>>>>>>>> Two different ip's on a DC will create your problems, remove
>>>>>>>>> one and it reboot the netlogon service on the DC. Why did you
>>>>>>>>> configure a second ip? Additional remove the loopback ip
>>>>>>>>> 127.0.0.1 from the DNS servers.
>>>>>>>>>
>>>>>>>>> What is the DNS server 192.168.140.66 from another subnet?
>>>>>>>>>
>>>>>>>>> Also if you not use IPv6 disable it's functionality according
>>>>>>>>> to this article:
>>>>>>>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/d
>>>>>>>>> is ab li ng-ipv6-on-windows-2008.aspx
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>> There is just one NIC active, the other one was deactivated.
>>>>>>>>>> The NIC has two internal IP adresses.
>>>>>>>>>>
>>>>>>>>>> ipconfig /all:
>>>>>>>>>>
>>>>>>>>>> Windows-IP-Konfiguration
>>>>>>>>>>
>>>>>>>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>>>>>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>>>>>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>>>>>>>> IP-Routing aktiviert . . . . . . : Nein
>>>>>>>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>>>>>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>>>>>>>> Ethernet-Adapter LAN-Verbindung:
>>>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>>>>>>>> Gigabit
>>>>>>>>>> Server Adapter
>>>>>>>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>>>> Verbindungslokale IPv6-Adresse . :
>>>>>>>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.51(Bevorzugt)
>>>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>>>> IPv4-Adresse . . . . . . . . . . : 192.168.146.52(Bevorzugt)
>>>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>>>>>>>> DNS-Server . . . . . . . . . . . : ::1
>>>>>>>>>> 192.168.146.52
>>>>>>>>>> 192.168.140.66
>>>>>>>>>> 127.0.0.1
>>>>>>>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>>>>>>> Tunneladapter LAN-Verbindung*:
>>>>>>>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>>>>>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>>>>> Hello Peter,
>>>>>>>>>>>
>>>>>>>>>>> Sounds like DNS, please post an unedited ipconfig /all from
>>>>>>>>>>> the server. The DC should not be multihomed, 2 NIC's with
>>>>>>>>>>> different ip addresses. One domain interal used and one to
>>>>>>>>>>> the ISP's DNS server for example.
>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> I have got some problems on two of my Windows 2008 servers.
>>>>>>>>>>>> Hardware: both are HP DL380 G5 with newest Firm- and
>>>>>>>>>>>> Software. Running Windows Server 2008 (full patched), AD,
>>>>>>>>>>>> DC, DNS Server, File- and Printserver, Trend Micro Virus
>>>>>>>>>>>> Scanner.
>>>>>>>>>>>>
>>>>>>>>>>>> Once a week, it seems that the network connections brakes
>>>>>>>>>>>> down,
>>>>>>>>>>>> although
>>>>>>>>>>>> users still can access shares, etc. Only printing is not
>>>>>>>>>>>> possible.
>>>>>>>>>>>> The
>>>>>>>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>>>>>>>> network connection.
>>>>>>>>>>>> I get different error messages in the eventlog like:
>>>>>>>>>>>> Error working group policy object. Name of the DC not found.
>>>>>>>>>>>> (...I
>>>>>>>>>>>> just
>>>>>>>>>>>> have the German version of the error messages!)
>>>>>>>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>>>>>>>> and so on.
>>>>>>>>>>>> Only rebooting the server solves the problem.
>>>>>>>>>>>> Any ideas?
>>>>>>>>>>>> Thank you very much for your help.
>
>

 

Hello Peter,

Again the error message states that you have DNS problem.

I suggest that you use the german newsgroup for your problem:
microsoft.public.de.german.windows.server.general
microsoft.public.de.german.windows.server.active_directory

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
>
> The server which had the problems, is only DC controller and "master
> server", that means that he has the FSMO roles.
> There is no bluescreen, normally you can't print and can't access
> network shares. In my opinion the error's come from the NIC.
> Error messages:
> Fehler bei der Verarbeitung der Gruppenrichtlinie. Der Name eines
> Domänencontrollers konnte nicht abgerufen werden. Dies kann auf einen
> Fehler bei der Namensauflösung zurückzuführen sein. Überprüfen Sie, ob
> DNS (Domain Name System) konfiguriert ist und richtig ausgeführt wird.
>
> Der DNS-Server konnte ein TCP-Socket nicht an die Adresse 0.0.0.0
> binden. Die Ereignisdaten enthalten den Fehlercode. Eine IP-Adresse
> von
> 0.0.0.0 bedeutet, dass ein Socket alle verfügbaren IP-Adressen des
> Computers verwendet (eine gültige Konfiguration).
> Starten Sie den DNS-Server bzw. den Computer neu.
> Der DNS-Server konnte den Socket für die Adresse 0.0.0.0 nicht öffnen.
> Überprüfen Sie, ob diese IP-Adresse auf dem Servercomputer gültig ist.
> Verwenden Sie im DNS-Manager das Eigenschaftenfenster des Servers und
> dort die Registerkarte "Schnittstellen", um diese Adresse
> gegebenenfalls von der Adressliste zu entfernen. Starten Sie den
> DNS-Server danach erneut. (Falls diese Adresse die einzige
> IP-Schnittstelle auf diesem Computer war, konnte der DNS-Server
> wahrscheinlich aufgrund dieses Fehlers nicht starten. In diesem Fall
> entfernen Sie den Eintrag "ListenAddress" in der Registrierung unter
> "\Services\DNS\Parameters", und führen Sie einen Neustart durch.)
>
> Wenn diese IP-Adresse auf dem Computer gültig ist, sollten Sie
> sicherstellen, dass keine andere Anwendung (z.B. ein anderer
> DNS-Server) aktiv ist, die versucht, auf den DNS-Port zuzugreifen.
>
> Weitere Informationen hierzu finden Sie in der Onlinehilfe im
> Abschnitt "DNS-Serverprotokollierungsreferenz".
>
> Die Konsistenzprüfung hat Probleme mit der folgenden
> Verzeichnispartition festgestellt.
>
> Verzeichnispartition:
> DC=ForestDnsZones,DC=domain,DC=int
> Es gibt für die Konsistenzprüfung nicht genügend
> Standortskonnektivitätsinformationen, um eine umfassende
> Gesamtstruktur-Replikationstopologie zu erstellen. Zudem besteht die
> Möglichkeit, dass mindestens ein Verzeichnisserver mit dieser
> Verzeichnispartition nicht in der Lage war, die
> Verzeichnispartitioninformationen zu replizieren. Dies liegt
> vermutlich an nicht zugreifbaren Verzeichnisservern.
>
> Benutzeraktion
> Führen Sie einen der folgenden Schritte aus:
> - Veröffentlichen Sie genügend Informationen über
> Standortkonnektivität,
> sodass die Konsistenzprüfung eine Route ermitteln kann, durch die die
> Verzeichnispartition diesen Standort erreichen kann. Diese Option wird
> empfohlen.
> - Fügen Sie von einem Verzeichnisdienst mit derselben
> Verzeichnispartition auf einem anderen Standort ein Verbindungsobjekt
> zu
> einem Verzeichnisdienst mit der Verzeichnispartition an diesem
> Standort
> hinzu.
> Wenn keine dieser beiden Tasks den Problemzustand behebt, überprüfen
> Sie die bisher durch die Konsistenzprüfung protokollierten Ereignisse,
> die die nicht zugreifbaren Verzeichnisserver identifizieren.
>
> Alle Verzeichnisdienste am folgenden Standort, die die
> Verzeichnispartition über diesen Transport replizieren können, sind
> zurzeit nicht verfügbar.
>
> Standort:
> CN=Innsbruck,CN=Sites,CN=Configuration,DC=domain,DC=int
> Verzeichnispartition:
> CN=Configuration,DC=domain,DC=int
> Transport:
> CN=IP,CN=Inter-Site
> Transports,CN=Sites,CN=Configuration,DC=domain,DC=int
> Best regards.
> Peter
> Meinolf Weber [MVP-DS] schrieb:
>
>> Hello Peter,
>>
>> So it seems that the ip address was not based on DNS? Strange in my
>> opinion, what does the application request from the servers?
>>
>> For your error please describe mroe detailed as "crashed", what
>> errors in the event viewer or on the server, blue screen?
>>
>> 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
>>> Hi
>>>
>>> I already changed what you suggested, without success.
>>> Today I had the problem on an 2008 Server which worked fine until
>>> this morning. It was the first that, that he "crashed"
>>> Then "something" crashed and I got the errors mentioned
>>> below.
>>> What I found out: It only happend on Windows Server 2008 Std.
>>> installed
>>> on brandnew HP ProLiant DL380 G5 and ProLiant DL320G5p.
>>> Best Regards.
>>> Peter
>>> Meinolf Weber [MVP-DS] schrieb:
>>>> Hello Peter,
>>>>
>>>> See the suggestion in my previous posting.
>>>>
>>>> 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
>>>>> I got the same error's again today.
>>>>> Any suggestions what I can still do?
>>>>> Best Regards.
>>>>> Peter
>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>> Hello Peter,
>>>>>>
>>>>>> If the software is written that badly , you should get the
>>>>>> programmer to fix that. If the ip is needed why not using one of
>>>>>> the available DNS servers and change the ip address to the old
>>>>>> one, assuming that DNS is the reason for the old ip?
>>>>>>
>>>>>> A DNS server from another subnet as secondary is ok.
>>>>>>
>>>>>> 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
>>>>>>> Hi
>>>>>>>
>>>>>>> We have some software (not standard software) which have some
>>>>>>> "hardcoded" links with the "old" ip adress. That's why I need
>>>>>>> the old adress. But I'll try to remove it.
>>>>>>>
>>>>>>> What about DNS, is it ok, that I use the DC (192.168.140.66)
>>>>>>> from another subnet as secondary DNS server?
>>>>>>>
>>>>>>> Best Regards.
>>>>>>>
>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>
>>>>>>>> Hello Peter,
>>>>>>>>
>>>>>>>> If the old DC is removed correct from the domain with demoting
>>>>>>>> there shouldn't be any service running what is using that ip
>>>>>>>> address. REMOVE that ip address from your DC's and the problems
>>>>>>>> will go.
>>>>>>>>
>>>>>>>> Please describe why you need this old address in detail, this
>>>>>>>> creates your problems.
>>>>>>>>
>>>>>>>> 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
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> My domain contains different subnets.
>>>>>>>>> 192.168.140.x
>>>>>>>>> 192.168.144.x
>>>>>>>>> 192.168.145.x
>>>>>>>>> 192.168.146.x
>>>>>>>>> Every local DC is DNS Server for his subnet.
>>>>>>>>> 192.168.140.66 is a redundant DNS Server for
>>>>>>>>> all subnets.
>>>>>>>>> I think I need the second IP on each DC because the second IP
>>>>>>>>> was
>>>>>>>>> the
>>>>>>>>> adress of the old server. (...they are replaced by new ones).
>>>>>>>>> Best regards.
>>>>>>>>> Peter
>>>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>>>> Hello Peter,
>>>>>>>>>>
>>>>>>>>>> Two different ip's on a DC will create your problems, remove
>>>>>>>>>> one and it reboot the netlogon service on the DC. Why did you
>>>>>>>>>> configure a second ip? Additional remove the loopback ip
>>>>>>>>>> 127.0.0.1 from the DNS servers.
>>>>>>>>>>
>>>>>>>>>> What is the DNS server 192.168.140.66 from another subnet?
>>>>>>>>>>
>>>>>>>>>> Also if you not use IPv6 disable it's functionality according
>>>>>>>>>> to this article:
>>>>>>>>>> http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19
>>>>>>>>>> /d is ab li ng-ipv6-on-windows-2008.aspx
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>>> There is just one NIC active, the other one was deactivated.
>>>>>>>>>>> The NIC has two internal IP adresses.
>>>>>>>>>>>
>>>>>>>>>>> ipconfig /all:
>>>>>>>>>>>
>>>>>>>>>>> Windows-IP-Konfiguration
>>>>>>>>>>>
>>>>>>>>>>> Hostname . . . . . . . . . . . . : SRVINNMAINII
>>>>>>>>>>> Prim"res DNS-Suffix . . . . . . . : domain.int
>>>>>>>>>>> Knotentyp . . . . . . . . . . . . : Hybrid
>>>>>>>>>>> IP-Routing aktiviert . . . . . . : Nein
>>>>>>>>>>> WINS-Proxy aktiviert . . . . . . : Nein
>>>>>>>>>>> DNS-Suffixsuchliste . . . . . . . : domain.int
>>>>>>>>>>> Ethernet-Adapter LAN-Verbindung:
>>>>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>>>>> Beschreibung. . . . . . . . . . . : HP NC373i Multifunction
>>>>>>>>>>> Gigabit
>>>>>>>>>>> Server Adapter
>>>>>>>>>>> Physikalische Adresse . . . . . . : 00-22-64-FB-00-46
>>>>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>>>>> Verbindungslokale IPv6-Adresse . :
>>>>>>>>>>> fe80::a88c:b1c4:f2a0:925c%10(Bevorzugt)
>>>>>>>>>>> IPv4-Adresse . . . . . . . . . . :
>>>>>>>>>>> 192.168.146.51(Bevorzugt)
>>>>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>> IPv4-Adresse . . . . . . . . . . :
>>>>>>>>>>> 192.168.146.52(Bevorzugt)
>>>>>>>>>>> Subnetzmaske . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>> Standardgateway . . . . . . . . . : 192.168.146.1
>>>>>>>>>>> DNS-Server . . . . . . . . . . . : ::1
>>>>>>>>>>> 192.168.146.52
>>>>>>>>>>> 192.168.140.66
>>>>>>>>>>> 127.0.0.1
>>>>>>>>>>> NetBIOS ber TCP/IP . . . . . . . : Aktiviert
>>>>>>>>>>> Tunneladapter LAN-Verbindung*:
>>>>>>>>>>> Medienstatus. . . . . . . . . . . : Medium getrennt
>>>>>>>>>>> Verbindungsspezifisches DNS-Suffix:
>>>>>>>>>>> Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
>>>>>>>>>>> Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>>>> DHCP aktiviert. . . . . . . . . . : Nein
>>>>>>>>>>> Autokonfiguration aktiviert . . . : Ja
>>>>>>>>>>> Meinolf Weber [MVP-DS] schrieb:
>>>>>>>>>>>> Hello Peter,
>>>>>>>>>>>>
>>>>>>>>>>>> Sounds like DNS, please post an unedited ipconfig /all from
>>>>>>>>>>>> the server. The DC should not be multihomed, 2 NIC's with
>>>>>>>>>>>> different ip addresses. One domain interal used and one to
>>>>>>>>>>>> the ISP's DNS server for example.
>>>>>>>>>>>>
>>>>>>>>>>>> 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
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have got some problems on two of my Windows 2008
>>>>>>>>>>>>> servers. Hardware: both are HP DL380 G5 with newest Firm-
>>>>>>>>>>>>> and Software. Running Windows Server 2008 (full patched),
>>>>>>>>>>>>> AD, DC, DNS Server, File- and Printserver, Trend Micro
>>>>>>>>>>>>> Virus Scanner.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Once a week, it seems that the network connections brakes
>>>>>>>>>>>>> down,
>>>>>>>>>>>>> although
>>>>>>>>>>>>> users still can access shares, etc. Only printing is not
>>>>>>>>>>>>> possible.
>>>>>>>>>>>>> The
>>>>>>>>>>>>> Symbol of the Trend Micro client looks like a broken
>>>>>>>>>>>>> network connection.
>>>>>>>>>>>>> I get different error messages in the eventlog like:
>>>>>>>>>>>>> Error working group policy object. Name of the DC not
>>>>>>>>>>>>> found.
>>>>>>>>>>>>> (...I
>>>>>>>>>>>>> just
>>>>>>>>>>>>> have the German version of the error messages!)
>>>>>>>>>>>>> PrintSpooler: ...DNS name couldn't be retrieved!
>>>>>>>>>>>>> and so on.
>>>>>>>>>>>>> Only rebooting the server solves the problem.
>>>>>>>>>>>>> Any ideas?
>>>>>>>>>>>>> Thank you very much for your help.