Windows Universal Storage Server 2003 quits working

[Guest IT_Cowboy]

I am having a problem with Windows Storage server . Every three weeks (to the

day) stops communicating with the domain controllers. At first it seems like

a network issue, but no other machines are affected (either servers or

workstations). The symptoms are as follows:

 

1. Cannot remote desktop into the machine, says domain controller cannot be

reached for authentication (UserEnv error ID 1053 occurs in Application log)

 

2. DFS Replication stops (of course it cannot find either DC, one of which

it replicates to Event ID 5002)

 

3. Local workstations can access files, remote workstations that need to

authenticate to acces files cannot

 

4. Not able to connect to internet through IE. IP configuration is correct

on NIC card.

 

5. Recieve LSASRV error in system log, Event ID 40960 and NETLOGON error,

Event ID 5719.

 

There are no scheduled (anything) that corrosponds with the timing of this,

and all processes, CPU, and memory seem normal. There are no additional error

messages as to why this happens and all hardware seems to be working

properly. A restart will fix this for the three week period.

 

The only software installed is Veritas backup Exec Agent (which works

normally), Veritas Continious Protection Server Agent (which quits working),

and Trend Micro Client (set to scan in off hours, no real time scans) There

is no known malware or viruses present on the system.

 

The Server is a Dell NX1950 with a MD3000 Raid Enclosure. All Firmware,

Bios, and MS patches are updated. If anyone has a clue as to what may be

causing this, or if you need more information, let me know. We have been

having this problem since October, and the Tech support at Dell does not seem

to be able to figure it out either.

 

--

To invent, you need a good imagination and a pile of junk.

Thomas A. Edison (1847 - 1931)

[Guest Meinolf Weber]

Re: Windows Universal Storage Server 2003 quits working

 

Hello IT_Cowboy,

 

To check some basics, please post an unedited ipconfig /all from the problem

server and your DNS/DC.

 

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 am having a problem with Windows Storage server . Every three weeks

> (to the day) stops communicating with the domain controllers. At first

> it seems like a network issue, but no other machines are affected

> (either servers or workstations). The symptoms are as follows:

>

> 1. Cannot remote desktop into the machine, says domain controller

> cannot be reached for authentication (UserEnv error ID 1053 occurs in

> Application log)

>

> 2. DFS Replication stops (of course it cannot find either DC, one of

> which it replicates to Event ID 5002)

>

> 3. Local workstations can access files, remote workstations that need

> to authenticate to acces files cannot

>

> 4. Not able to connect to internet through IE. IP configuration is

> correct on NIC card.

>

> 5. Recieve LSASRV error in system log, Event ID 40960 and NETLOGON

> error, Event ID 5719.

>

> There are no scheduled (anything) that corrosponds with the timing of

> this, and all processes, CPU, and memory seem normal. There are no

> additional error messages as to why this happens and all hardware

> seems to be working properly. A restart will fix this for the three

> week period.

>

> The only software installed is Veritas backup Exec Agent (which works

> normally), Veritas Continious Protection Server Agent (which quits

> working), and Trend Micro Client (set to scan in off hours, no real

> time scans) There is no known malware or viruses present on the

> system.

>

> The Server is a Dell NX1950 with a MD3000 Raid Enclosure. All

> Firmware, Bios, and MS patches are updated. If anyone has a clue as to

> what may be causing this, or if you need more information, let me

> know. We have been having this problem since October, and the Tech

> support at Dell does not seem to be able to figure it out either.

>

[Guest IT_Cowboy]

Re: Windows Universal Storage Server 2003 quits working

 

Ok, here is the IPConfig, although I already restarted this server last

night, I can assure you that the IPConfig is the same when it is "Down"

 

SC-3 (Windows UDS Server 2003 SP2)

Windows IP Configuration

 

 

 

Host Name . . . . . . . . . . . . : sc-3

 

Primary Dns Suffix . . . . . . . : sc.local

 

Node Type . . . . . . . . . . . . : Unknown

 

IP Routing Enabled. . . . . . . . : No

 

WINS Proxy Enabled. . . . . . . . : No

 

DNS Suffix Search List. . . . . . : sc.local

 

 

 

Ethernet adapter Local Area Connection 2:

 

 

 

Connection-specific DNS Suffix . :

 

Description . . . . . . . . . . . : Intel® PRO/1000 PT Dual Port Server

Adapter #2

 

Physical Address. . . . . . . . . : 00-15-17-3B-26-01

 

DHCP Enabled. . . . . . . . . . . : No

 

IP Address. . . . . . . . . . . . : 192.168.1.16

 

Subnet Mask . . . . . . . . . . . : 255.255.255.0

 

Default Gateway . . . . . . . . . : 192.168.1.1

 

DNS Servers . . . . . . . . . . . : 192.168.1.8

 

192.168.168.5

 

 

 

Ethernet adapter Backup Connection:

 

 

 

Connection-specific DNS Suffix . :

 

Description . . . . . . . . . . . : Intel® PRO/1000 PT Dual Port Server

Adapter

 

Physical Address. . . . . . . . . : 00-15-17-3B-26-00

 

DHCP Enabled. . . . . . . . . . . : No

 

IP Address. . . . . . . . . . . . : 10.0.1.2

 

Subnet Mask . . . . . . . . . . . : 255.0.0.0

 

Default Gateway . . . . . . . . . : 10.0.1.1

 

DNS Servers . . . . . . . . . . . : 10.0.1.1

 

SC-0 (DC)(Windows Server 2003 SP2)

 

Windows IP Configuration

 

 

 

Host Name . . . . . . . . . . . . : sc-0

 

Primary Dns Suffix . . . . . . . : sc.local

 

Node Type . . . . . . . . . . . . : Hybrid

 

IP Routing Enabled. . . . . . . . : No

 

WINS Proxy Enabled. . . . . . . . : No

 

DNS Suffix Search List. . . . . . : sc.local

 

 

 

Ethernet adapter Backup Connection:

 

 

 

Connection-specific DNS Suffix . :

 

Description . . . . . . . . . . . : Intel® PRO/1000 MT Dual Port Server

Adapter #2

 

Physical Address. . . . . . . . . : 00-04-23-DF-96-37

 

DHCP Enabled. . . . . . . . . . . : No

 

IP Address. . . . . . . . . . . . : 10.0.1.1

 

Subnet Mask . . . . . . . . . . . : 255.0.0.0

 

Default Gateway . . . . . . . . . :

 

NetBIOS over Tcpip. . . . . . . . : Disabled

 

 

 

Ethernet adapter Local Area Connection:

 

 

 

Connection-specific DNS Suffix . :

 

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet

 

Physical Address. . . . . . . . . : 00-0B-DB-AD-03-20

 

DHCP Enabled. . . . . . . . . . . : No

 

IP Address. . . . . . . . . . . . : 192.168.1.8

 

Subnet Mask . . . . . . . . . . . : 255.255.255.0

 

Default Gateway . . . . . . . . . : 192.168.1.1

 

DNS Servers . . . . . . . . . . . : 192.168.1.8

 

192.168.1.1

 

SC-4-s rdamin(DC, Branch Office, DFS Target)(Windows Server 2003 R2 SP2)

Windows IP Configuration

 

 

 

Host Name . . . . . . . . . . . . : sc-4-s

 

Primary Dns Suffix . . . . . . . : sc.local

 

Node Type . . . . . . . . . . . . : Unknown

 

IP Routing Enabled. . . . . . . . : No

 

WINS Proxy Enabled. . . . . . . . : No

 

DNS Suffix Search List. . . . . . : sc.local

 

 

 

Ethernet adapter Local Area Connection:

 

 

 

Connection-specific DNS Suffix . :

 

Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE

(NDIS VBD Client)

 

Physical Address. . . . . . . . . : 00-19-B9-C4-02-40

 

DHCP Enabled. . . . . . . . . . . : No

 

IP Address. . . . . . . . . . . . : 192.168.168.5

 

Subnet Mask . . . . . . . . . . . : 255.255.255.0

 

Default Gateway . . . . . . . . . : 192.168.168.1

 

DNS Servers . . . . . . . . . . . : 192.168.168.5

 

192.168.1.8

 

204.130.255.3

 

64.122.32.71

 

 

 

--

To invent, you need a good imagination and a pile of junk.

Thomas A. Edison (1847 - 1931)

 

 

 

"Meinolf Weber" wrote:

> Hello IT_Cowboy,

>

> To check some basics, please post an unedited ipconfig /all from the problem

> server and your DNS/DC.

>

> 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 am having a problem with Windows Storage server . Every three weeks

> > (to the day) stops communicating with the domain controllers. At first

> > it seems like a network issue, but no other machines are affected

> > (either servers or workstations). The symptoms are as follows:

> >

> > 1. Cannot remote desktop into the machine, says domain controller

> > cannot be reached for authentication (UserEnv error ID 1053 occurs in

> > Application log)

> >

> > 2. DFS Replication stops (of course it cannot find either DC, one of

> > which it replicates to Event ID 5002)

> >

> > 3. Local workstations can access files, remote workstations that need

> > to authenticate to acces files cannot

> >

> > 4. Not able to connect to internet through IE. IP configuration is

> > correct on NIC card.

> >

> > 5. Recieve LSASRV error in system log, Event ID 40960 and NETLOGON

> > error, Event ID 5719.

> >

> > There are no scheduled (anything) that corrosponds with the timing of

> > this, and all processes, CPU, and memory seem normal. There are no

> > additional error messages as to why this happens and all hardware

> > seems to be working properly. A restart will fix this for the three

> > week period.

> >

> > The only software installed is Veritas backup Exec Agent (which works

> > normally), Veritas Continious Protection Server Agent (which quits

> > working), and Trend Micro Client (set to scan in off hours, no real

> > time scans) There is no known malware or viruses present on the

> > system.

> >

> > The Server is a Dell NX1950 with a MD3000 Raid Enclosure. All

> > Firmware, Bios, and MS patches are updated. If anyone has a clue as to

> > what may be causing this, or if you need more information, let me

> > know. We have been having this problem since October, and the Tech

> > support at Dell does not seem to be able to figure it out either.

> >

>

>

>

[Guest Meinolf Weber]

Re: Windows Universal Storage Server 2003 quits working

 

Hello IT_Cowboy,

 

On sc-4-s you have on the NIC settings 204.130.255.3 and 64.122.32.71 configured,

i assume this are the ISP's DNS server. You have to remove them here and

configure them in the DNS management console under server properties FORWARDERS

TAB. Here add the addresses.

 

Also you are using multihomed machines, especially the DC, which is a bad

solution. See here why, even it is a lot info:

 

1. Domain Controllers should not be multi-homed

2. Being a VPN Server and even simply running RRAS makes it multi-homed.

3. DNS,..even just all by itself, is better on a single homed machine.

4. Domain Controllers with the PDF Role are automatically Domain Master

Browser. Master Browsers should not be multi-homed

 

272294 - Active Directory Communication Fails on Multihomed Domain Controllers

http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

 

191611 - Symptoms of Multihomed Browsers

http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611

 

Phillip Windell

http://www.wandtv.com

 

The views expressed, are my own and not those of my employer, or Microsoft,

or anyone else associated with me, including my cats. -----------------------------------------------------

 

 

See also:

 

Multihomed DCs, DNS, RRAS servers.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

Below are the manual steps in more detail, which I had outlined in the above

paragraph:

 

Honestly, multi-homed DCs are not recommended because of the associated issues

that can occur, as you've encountered. We usually recommend purchasing an

inexpensive Linksys, DLink, etc, Cable/DSL router to perform NAT for you,

take out the extra NIC off the DC, but still let the DC handle DHCP (and

not the router).

 

Little background on AD and DNS:

First, just to get this out of the way, if you have your ISP's DNS addresses

in your IP configuration (DCs and clients), they need to be REMOVED.

 

If the ISP's DNS is in there, this will cause additional problems.

 

Also, AD registers certain records in DNS in the form of SRV records that

signify AD's resource and service locations. When there are multiple NICs,

each NIC registers. IF a client, or another DC queries DNS for this DC, it

may get the wrong record. One factor controlling this is Round Robin. If

a DC or client on another subnet that the DC is not configured on queries

for it, Round Robin will kick in offering one or the other. If the wrong

one gets offered, it may not have a route to it. On the other hand, Subnetmask

Priortization will ensure a querying client will get an IP that corresponds

to the subnet it's on, which will work. To insure everything works, stick

with one NIC.

 

Since this DC is multi-homed, it requires additional configuration to prevent

the public interface addresses from being registered in DNS. This creates

a problem for internal clients locating AD to authenticate and find other

services and resources such as the Global Catalog, file sharing and the SYSVOL

DFS share and can cause GPO errors with Userenv 1000 events to be logged,

authenticating to shares and printers, logging on takes forever, among numerous

other issues.

 

But if you like, there are some registry changes to eliminate the registration

of the external NIC. Here's the whole list of manual steps to follow.

 

But believe me, it's much easier to just get a separate NAT device or multihome

a non-DC then having to alter the DC. - Good luck!

 

1. Insure that all the NICS only point to your internal DNS server(s) only

and none others, such as your ISP's DNS servers' IP addresses.

 

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,

move the internal NIC (the network that AD is on) to the top of the binding

order (top of the list).

 

3. Disable the ability for the outer NIC to register. The procedure, as

mentioned, involves identifying the outer NIC's GUID number. This link will

show you how:

246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per

NIC too):

http://support.microsoft.com/?id=246804

 

4. Disable NetBIOS on the outside NIC. That is performed by choosing to

disable NetBIOS in IP Properties, Advanced, and you will find that under the

"WINS" tab. You may want to look at step #3 in the article to show you how

to disable NetBIOS on the RRAS interfaces if this is a RRAS server.

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface

[Registry Entry]:

http://support.microsoft.com/?id=296379

 

Note: A standard Windows service, called the "Browser service", provides

the list of machines, workgroup and domain names that you see in "My Network

Places" (or the legacy term "Network Neighborhood"). The Browser service

relies on the NetBIOS service. One major requirement of NetBIOS service is

a machine can only have one name to one IP address. It's sort of a fingerprint.

You can't have two brothers named Darrell. A multihomed machine will cause

duplicate name errors on itself because Windows sees itself with the same

name in the Browse List (My Network Places), but with different IPs. You

can only have one, hence the error generated.

 

5. Disable the "File and Print Service" and disable the "MS Client Service"

on the outer NIC. That is done in NIC properties by unchecking the respective

service under the general properties page. If you need these services on

the outside NIC (which is unlikely), which allow other machines to connect

to your machine for accessing resource on your machine (shared folders, printers,

etc.), then you will probably need to keep them enabled.

 

6. Uncheck "Register this connection" under IP properties, Advanced settings,

"DNS" tab.

 

7. Delete the outer NIC IP address, disable Netlogon registration, and manually

create the required records

 

a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's

IP references for the "LdapIpAddress". If this is a GC, you will need to

delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS

console, under the zone name, you will see the _msdcs folder. Under that,

you will see the _gc folder. To the right, you will see the IP address referencing

the GC address. That is called the GcIpAddress. Delete the IP addresses referencing

the outer NIC.

 

i. To stop these two records from registering that information,

use the steps provided in the links below:

Private Network Interfaces on a Domain Controller Are Registered in

DNShttp://support.microsoft.com/?id=295328

 

ii. The one section of the article that disables these records is done with

this registry entry:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

(Create this Multi-String Value under it):

Registry value: DnsAvoidRegisterRecords

Data type: REG_MULTI_SZ

Values: LdapIpAddress

GcIpAddress

 

iii. Here is more information on these and other Netlogon Service records:

 

Restrict the DNS SRV resource records updated by the Netlogon service

 

[including GC]:

 

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_dns_pro_no_rr_in_ad.asp

 

b. Then you will need to manually create these two records in DNS with the

IP addresses that you need for the DC. To create the

 

LdapIpAddress, create a new host under the domain, but leave the "hostname"

field blank, and provide the internal IP of the DC, which results in a

record that looks like:

(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative

purposes)

 

i. You need to also manually create the GcIpAddress as well, if this is a

GC. That would be under the _msdcs._gc SRV record under the zone. It is created

in the same fashion as the LdapIpAddress mentioned above.

 

8. In the DNS console, right click the server name, choose properties, then

under the "Interfaces" tab, force it only to listen to the internal NIC's

IP address, and not the IP address of the outer NIC.

 

9. Since this is also a DNS server, the IPs from all NICs will register,

even if you tell it not to in the NIC properties. See this to show you how

to stop that behavior (this procedure is for Windows 2000, but will also

work for Windows 2003):

275554 - The Host's A Record Is Registered in DNS After You Choose Not to

Register the Connection's Address:

http://support.microsoft.com/?id=275554

 

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if

not sure which DNS to forward to until you've got the DNS address of your

ISP.

How to set a forwarder? Good question. Depending on your operating

system,choose one of the following articles:

 

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000 http://support.microsoft.com/?id=300202&FR=1

 

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003

(How to configure a forwarder):

http://support.microsoft.com/d/id?=323380

 

Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

 

<==*** Some additional reading ***==>

More links to read up and understand what is going on:

 

292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain

Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and

unwanted IPs registering]:

http://support.microsoft.com/?id=292822

 

Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

 

246804 - How to enable or disable DNS updates in Windows 2000 and in Windows

Server 2003

http://support.microsoft.com/?id=246804

 

295328 - Private Network Interfaces on a Domain Controller Are Registered in

DNS

[also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent

private IP]:

http://support.microsoft.com/?id=295328

 

306602 - How to Optimize the Location of a DC or GC That Resides Outside of

a Client's

Site [includes info LdapIpAddress and GcIpAddress information and the SRV

mnemonic values]:

http://support.microsoft.com/?id=306602

 

825036 - Best practices for DNS client settings in Windows 2000 Server and

in Windows Server 2003 (including how-to configure a forwarder): http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

 

291382 - Frequently asked questions about Windows 2000 DNS and Windows

Server 2003 DNS

http://support.microsoft.com/?id=291382

 

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface

[Registry Entry]:

http://support.microsoft.com/?id=296379

 

Rid Pool Errors and other mutlhomed DC errors, and how to configure a multihomed

DC, Ace Fekay, 24 Feb 2006 http://www.ureader.com/message/3244572.aspx

 

_________________________ +++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

--

Regards,

Ace

 

 

This posting is provided "AS-IS" with no warranties or guarantees and confers

no rights.

 

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP

Microsoft MVP - Directory Services

Microsoft Certified Trainer

 

Infinite Diversities in Infinite Combinations

 

Having difficulty reading or finding responses to your post?

Instead of the website you're using, try using OEx (Outlook Express

or any other newsreader), and configure a news account, pointing to

news.microsoft.com. Anonymous access. It's free - no username or password

required nor do you need a Newsgroup Usenet account with your ISP. It

connects directly to the Microsoft Public Newsgroups. OEx allows you

o easily find, track threads, cross-post, sort by date, poster's name,

watched threads or subject. It's easy:

 

How to Configure OEx for Internet News

http://support.microsoft.com/?id=171164

 

 

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

> sc-4-s

>

[Guest IT_Cowboy]

Re: Windows Universal Storage Server 2003 quits working

 

ok, will fix SC-4-s NIC settings.. good idea.

 

The problem is other than that though.. I am aware of multihomed settings on

the DC. as a matter of fact we already looked into this. The 10.* address

range does not register in DNS. That is a seperate NIC used solely for Backup

streaming, which never has stopped working. In addition, SC-3 is the one that

loses communication, SC-0 and SC-4-s replicate fine. It is only after the

exact 3 week period that the file replication problems (and other symptoms)

occur on SC-3. During that time DC replication, and all other functions of

every other server work fine.

 

If there is a problem with multiple NICs on SC-3, then it needs to be

figured out, because two more will be added when this problem is fixed so we

can start using it as a iSCSI for other servers.

 

did I mention before that when this problem happens, I can still ping sc-0

and do a nslookup on sc-0 with the correct results..

 

Thank you for your help though, any further ideas will be greatly

appreciated..

 

--

To invent, you need a good imagination and a pile of junk.

Thomas A. Edison (1847 - 1931)

 

 

 

"Meinolf Weber" wrote:

> Hello IT_Cowboy,

>

> On sc-4-s you have on the NIC settings 204.130.255.3 and 64.122.32.71 configured,

> i assume this are the ISP's DNS server. You have to remove them here and

> configure them in the DNS management console under server properties FORWARDERS

> TAB. Here add the addresses.

>

> Also you are using multihomed machines, especially the DC, which is a bad

> solution. See here why, even it is a lot info:

>

> 1. Domain Controllers should not be multi-homed

> 2. Being a VPN Server and even simply running RRAS makes it multi-homed.

> 3. DNS,..even just all by itself, is better on a single homed machine.

> 4. Domain Controllers with the PDF Role are automatically Domain Master

> Browser. Master Browsers should not be multi-homed

>

> 272294 - Active Directory Communication Fails on Multihomed Domain Controllers

> http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

>

> 191611 - Symptoms of Multihomed Browsers

> http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611

>

> Phillip Windell

> http://www.wandtv.com

>

> The views expressed, are my own and not those of my employer, or Microsoft,

> or anyone else associated with me, including my cats. -----------------------------------------------------

>

>

> See also:

>

> Multihomed DCs, DNS, RRAS servers.

> +++++++++++++++++++++++++++++++++++++++++++++++++++++++

> +++++++++++++++++++++++++++++++++++++++++++++++++++++++

> Below are the manual steps in more detail, which I had outlined in the above

> paragraph:

>

> Honestly, multi-homed DCs are not recommended because of the associated issues

> that can occur, as you've encountered. We usually recommend purchasing an

> inexpensive Linksys, DLink, etc, Cable/DSL router to perform NAT for you,

> take out the extra NIC off the DC, but still let the DC handle DHCP (and

> not the router).

>

> Little background on AD and DNS:

> First, just to get this out of the way, if you have your ISP's DNS addresses

> in your IP configuration (DCs and clients), they need to be REMOVED.

>

> If the ISP's DNS is in there, this will cause additional problems.

>

> Also, AD registers certain records in DNS in the form of SRV records that

> signify AD's resource and service locations. When there are multiple NICs,

> each NIC registers. IF a client, or another DC queries DNS for this DC, it

> may get the wrong record. One factor controlling this is Round Robin. If

> a DC or client on another subnet that the DC is not configured on queries

> for it, Round Robin will kick in offering one or the other. If the wrong

> one gets offered, it may not have a route to it. On the other hand, Subnetmask

> Priortization will ensure a querying client will get an IP that corresponds

> to the subnet it's on, which will work. To insure everything works, stick

> with one NIC.

>

> Since this DC is multi-homed, it requires additional configuration to prevent

> the public interface addresses from being registered in DNS. This creates

> a problem for internal clients locating AD to authenticate and find other

> services and resources such as the Global Catalog, file sharing and the SYSVOL

> DFS share and can cause GPO errors with Userenv 1000 events to be logged,

> authenticating to shares and printers, logging on takes forever, among numerous

> other issues.

>

> But if you like, there are some registry changes to eliminate the registration

> of the external NIC. Here's the whole list of manual steps to follow.

>

> But believe me, it's much easier to just get a separate NAT device or multihome

> a non-DC then having to alter the DC. - Good luck!

>

> 1. Insure that all the NICS only point to your internal DNS server(s) only

> and none others, such as your ISP's DNS servers' IP addresses.

>

> 2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,

> move the internal NIC (the network that AD is on) to the top of the binding

> order (top of the list).

>

> 3. Disable the ability for the outer NIC to register. The procedure, as

> mentioned, involves identifying the outer NIC's GUID number. This link will

> show you how:

> 246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per

> NIC too):

> http://support.microsoft.com/?id=246804

>

> 4. Disable NetBIOS on the outside NIC. That is performed by choosing to

> disable NetBIOS in IP Properties, Advanced, and you will find that under the

> "WINS" tab. You may want to look at step #3 in the article to show you how

> to disable NetBIOS on the RRAS interfaces if this is a RRAS server.

> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface

> [Registry Entry]:

> http://support.microsoft.com/?id=296379

>

> Note: A standard Windows service, called the "Browser service", provides

> the list of machines, workgroup and domain names that you see in "My Network

> Places" (or the legacy term "Network Neighborhood"). The Browser service

> relies on the NetBIOS service. One major requirement of NetBIOS service is

> a machine can only have one name to one IP address. It's sort of a fingerprint.

> You can't have two brothers named Darrell. A multihomed machine will cause

> duplicate name errors on itself because Windows sees itself with the same

> name in the Browse List (My Network Places), but with different IPs. You

> can only have one, hence the error generated.

>

> 5. Disable the "File and Print Service" and disable the "MS Client Service"

> on the outer NIC. That is done in NIC properties by unchecking the respective

> service under the general properties page. If you need these services on

> the outside NIC (which is unlikely), which allow other machines to connect

> to your machine for accessing resource on your machine (shared folders, printers,

> etc.), then you will probably need to keep them enabled.

>

> 6. Uncheck "Register this connection" under IP properties, Advanced settings,

> "DNS" tab.

>

> 7. Delete the outer NIC IP address, disable Netlogon registration, and manually

> create the required records

>

> a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's

> IP references for the "LdapIpAddress". If this is a GC, you will need to

> delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS

> console, under the zone name, you will see the _msdcs folder. Under that,

> you will see the _gc folder. To the right, you will see the IP address referencing

> the GC address. That is called the GcIpAddress. Delete the IP addresses referencing

> the outer NIC.

>

> i. To stop these two records from registering that information,

> use the steps provided in the links below:

> Private Network Interfaces on a Domain Controller Are Registered in

> DNShttp://support.microsoft.com/?id=295328

>

> ii. The one section of the article that disables these records is done with

> this registry entry:

>

> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

> (Create this Multi-String Value under it):

> Registry value: DnsAvoidRegisterRecords

> Data type: REG_MULTI_SZ

> Values: LdapIpAddress

> GcIpAddress

>

> iii. Here is more information on these and other Netlogon Service records:

>

> Restrict the DNS SRV resource records updated by the Netlogon service

>

> [including GC]:

>

> http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_dns_pro_no_rr_in_ad.asp

>

> b. Then you will need to manually create these two records in DNS with the

> IP addresses that you need for the DC. To create the

>

> LdapIpAddress, create a new host under the domain, but leave the "hostname"

> field blank, and provide the internal IP of the DC, which results in a

> record that looks like:

> (same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative

> purposes)

>

> i. You need to also manually create the GcIpAddress as well, if this is a

> GC. That would be under the _msdcs._gc SRV record under the zone. It is created

> in the same fashion as the LdapIpAddress mentioned above.

>

> 8. In the DNS console, right click the server name, choose properties, then

> under the "Interfaces" tab, force it only to listen to the internal NIC's

> IP address, and not the IP address of the outer NIC.

>

> 9. Since this is also a DNS server, the IPs from all NICs will register,

> even if you tell it not to in the NIC properties. See this to show you how

> to stop that behavior (this procedure is for Windows 2000, but will also

> work for Windows 2003):

> 275554 - The Host's A Record Is Registered in DNS After You Choose Not to

> Register the Connection's Address:

> http://support.microsoft.com/?id=275554

>

> 10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if

> not sure which DNS to forward to until you've got the DNS address of your

> ISP.

> How to set a forwarder? Good question. Depending on your operating

> system,choose one of the following articles:

>

> 300202 - HOW TO: Configure DNS for Internet Access in Windows 2000 http://support.microsoft.com/?id=300202&FR=1

>

> 323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003

> (How to configure a forwarder):

> http://support.microsoft.com/d/id?=323380

>

> Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

>

> <==*** Some additional reading ***==>

> More links to read up and understand what is going on:

>

> 292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain

> Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and

> unwanted IPs registering]:

> http://support.microsoft.com/?id=292822

>

> Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

>

> 246804 - How to enable or disable DNS updates in Windows 2000 and in Windows

> Server 2003

> http://support.microsoft.com/?id=246804

>

> 295328 - Private Network Interfaces on a Domain Controller Are Registered in

> DNS

> [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent

> private IP]:

> http://support.microsoft.com/?id=295328

>

> 306602 - How to Optimize the Location of a DC or GC That Resides Outside of

> a Client's

> Site [includes info LdapIpAddress and GcIpAddress information and the SRV

> mnemonic values]:

> http://support.microsoft.com/?id=306602

>

> 825036 - Best practices for DNS client settings in Windows 2000 Server and

> in Windows Server 2003 (including how-to configure a forwarder): http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

>

> 291382 - Frequently asked questions about Windows 2000 DNS and Windows

> Server 2003 DNS

> http://support.microsoft.com/?id=291382

>

> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface

> [Registry Entry]:

> http://support.microsoft.com/?id=296379

>

> Rid Pool Errors and other mutlhomed DC errors, and how to configure a multihomed

> DC, Ace Fekay, 24 Feb 2006 http://www.ureader.com/message/3244572.aspx

>

> _________________________ +++++++++++++++++++++++++++++++++++++++++++++++++++++++

> +++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++

>

> --

> Regards,

> Ace

>

>

> This posting is provided "AS-IS" with no warranties or guarantees and confers

> no rights.

>

> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP

> Microsoft MVP - Directory Services

> Microsoft Certified Trainer

>

> Infinite Diversities in Infinite Combinations

>

> Having difficulty reading or finding responses to your post?

> Instead of the website you're using, try using OEx (Outlook Express

> or any other newsreader), and configure a news account, pointing to

> news.microsoft.com. Anonymous access. It's free - no username or password

> required nor do you need a Newsgroup Usenet account with your ISP. It

> connects directly to the Microsoft Public Newsgroups. OEx allows you

> o easily find, track threads, cross-post, sort by date, poster's name,

> watched threads or subject. It's easy:

>

> How to Configure OEx for Internet News

> http://support.microsoft.com/?id=171164

>

>

> 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

>

> > sc-4-s

> >

>

>

>

[Guest HeadScratcher]

RE: Windows Universal Storage Server 2003 quits working

 

 

 

"IT_Cowboy" wrote:

> I am having a problem with Windows Storage server . Every three weeks (to the

> day) stops communicating with the domain controllers. At first it seems like

> a network issue, but no other machines are affected (either servers or

> workstations). The symptoms are as follows:

>

> 1. Cannot remote desktop into the machine, says domain controller cannot be

> reached for authentication (UserEnv error ID 1053 occurs in Application log)

>

> 2. DFS Replication stops (of course it cannot find either DC, one of which

> it replicates to Event ID 5002)

>

> 3. Local workstations can access files, remote workstations that need to

> authenticate to acces files cannot

>

> 4. Not able to connect to internet through IE. IP configuration is correct

> on NIC card.

>

> 5. Recieve LSASRV error in system log, Event ID 40960 and NETLOGON error,

> Event ID 5719.

>

> There are no scheduled (anything) that corrosponds with the timing of this,

> and all processes, CPU, and memory seem normal. There are no additional error

> messages as to why this happens and all hardware seems to be working

> properly. A restart will fix this for the three week period.

>

> The only software installed is Veritas backup Exec Agent (which works

> normally), Veritas Continious Protection Server Agent (which quits working),

> and Trend Micro Client (set to scan in off hours, no real time scans) There

> is no known malware or viruses present on the system.

>

> The Server is a Dell NX1950 with a MD3000 Raid Enclosure. All Firmware,

> Bios, and MS patches are updated. If anyone has a clue as to what may be

> causing this, or if you need more information, let me know. We have been

> having this problem since October, and the Tech support at Dell does not seem

> to be able to figure it out either.

>

> --

> To invent, you need a good imagination and a pile of junk.

> Thomas A. Edison (1847 - 1931)

>

[Guest HeadScratcher]

RE: Windows Universal Storage Server 2003 quits working

 

Hello IT_Cowboy,

 

I know this doesn't help you at all but...

 

We have the exact same issue. NX1950 / MD3000. We get exactly two weeks

before symptoms arise EXACTLY as you describe. Numerous support calls with

Dell to No avail. The only solution this far is a reboot (which is EXTREMELY

painful because this box is a SAN hosting nearly a dozen virtual servers)

 

"IT_Cowboy" wrote:

> I am having a problem with Windows Storage server . Every three weeks (to the

> day) stops communicating with the domain controllers. At first it seems like

> a network issue, but no other machines are affected (either servers or

> workstations). The symptoms are as follows:

>

> 1. Cannot remote desktop into the machine, says domain controller cannot be

> reached for authentication (UserEnv error ID 1053 occurs in Application log)

>

> 2. DFS Replication stops (of course it cannot find either DC, one of which

> it replicates to Event ID 5002)

>

> 3. Local workstations can access files, remote workstations that need to

> authenticate to acces files cannot

>

> 4. Not able to connect to internet through IE. IP configuration is correct

> on NIC card.

>

> 5. Recieve LSASRV error in system log, Event ID 40960 and NETLOGON error,

> Event ID 5719.

>

> There are no scheduled (anything) that corrosponds with the timing of this,

> and all processes, CPU, and memory seem normal. There are no additional error

> messages as to why this happens and all hardware seems to be working

> properly. A restart will fix this for the three week period.

>

> The only software installed is Veritas backup Exec Agent (which works

> normally), Veritas Continious Protection Server Agent (which quits working),

> and Trend Micro Client (set to scan in off hours, no real time scans) There

> is no known malware or viruses present on the system.

>

> The Server is a Dell NX1950 with a MD3000 Raid Enclosure. All Firmware,

> Bios, and MS patches are updated. If anyone has a clue as to what may be

> causing this, or if you need more information, let me know. We have been

> having this problem since October, and the Tech support at Dell does not seem

> to be able to figure it out either.

>

> --

> To invent, you need a good imagination and a pile of junk.

> Thomas A. Edison (1847 - 1931)

>

[Guest IT_Cowboy]

RE: Windows Universal Storage Server 2003 quits working

 

Exactly!.. we are going to be using it for Virtual servers, but not until

this problem is resolved.. I actually got a tech at Dell that seems

intrested. If we find a solution I will let you know the steps we took. I

will reply here and then we can get in contact.. I will have to let the tech

know that there is someone else having the same problem..

 

One thing we have found out is to watch the SMProv~1.exe in the task

manager. It does not seem to be letting loose it's handles. they just keep

climbing.. Have not figured out a solution yet, but it is something..

 

--

To invent, you need a good imagination and a pile of junk.

Thomas A. Edison (1847 - 1931)

 

 

 

"HeadScratcher" wrote:

> Hello IT_Cowboy,

>

> I know this doesn't help you at all but...

>

> We have the exact same issue. NX1950 / MD3000. We get exactly two weeks

> before symptoms arise EXACTLY as you describe. Numerous support calls with

> Dell to No avail. The only solution this far is a reboot (which is EXTREMELY

> painful because this box is a SAN hosting nearly a dozen virtual servers)

>

> "IT_Cowboy" wrote:

>

> > I am having a problem with Windows Storage server . Every three weeks (to the

> > day) stops communicating with the domain controllers. At first it seems like

> > a network issue, but no other machines are affected (either servers or

> > workstations). The symptoms are as follows:

> >

> > 1. Cannot remote desktop into the machine, says domain controller cannot be

> > reached for authentication (UserEnv error ID 1053 occurs in Application log)

> >

> > 2. DFS Replication stops (of course it cannot find either DC, one of which

> > it replicates to Event ID 5002)

> >

> > 3. Local workstations can access files, remote workstations that need to

> > authenticate to acces files cannot

> >

> > 4. Not able to connect to internet through IE. IP configuration is correct

> > on NIC card.

> >

> > 5. Recieve LSASRV error in system log, Event ID 40960 and NETLOGON error,

> > Event ID 5719.

> >

> > There are no scheduled (anything) that corrosponds with the timing of this,

> > and all processes, CPU, and memory seem normal. There are no additional error

> > messages as to why this happens and all hardware seems to be working

> > properly. A restart will fix this for the three week period.

> >

> > The only software installed is Veritas backup Exec Agent (which works

> > normally), Veritas Continious Protection Server Agent (which quits working),

> > and Trend Micro Client (set to scan in off hours, no real time scans) There

> > is no known malware or viruses present on the system.

> >

> > The Server is a Dell NX1950 with a MD3000 Raid Enclosure. All Firmware,

> > Bios, and MS patches are updated. If anyone has a clue as to what may be

> > causing this, or if you need more information, let me know. We have been

> > having this problem since October, and the Tech support at Dell does not seem

> > to be able to figure it out either.

> >

> > --

> > To invent, you need a good imagination and a pile of junk.

> > Thomas A. Edison (1847 - 1931)

> >

[Guest IT_Cowboy]

RE: Windows Universal Storage Server 2003 quits working

 

Is there any way I could get your support number from Dell, I will give it to

our guy then and maybe he could compare the data from both cases and find a

solution for both of us.. you can email me at gnaber@NOSPAM.skillings.com. Of

course you have to remove the NOSPAM. from the address..

--

To invent, you need a good imagination and a pile of junk.

Thomas A. Edison (1847 - 1931)

 

 

 

"HeadScratcher" wrote:

> Hello IT_Cowboy,

>

> I know this doesn't help you at all but...

>

> We have the exact same issue. NX1950 / MD3000. We get exactly two weeks

> before symptoms arise EXACTLY as you describe. Numerous support calls with

> Dell to No avail. The only solution this far is a reboot (which is EXTREMELY

> painful because this box is a SAN hosting nearly a dozen virtual servers)

>

> "IT_Cowboy" wrote:

>

> > I am having a problem with Windows Storage server . Every three weeks (to the

> > day) stops communicating with the domain controllers. At first it seems like

> > a network issue, but no other machines are affected (either servers or

> > workstations). The symptoms are as follows:

> >

> > 1. Cannot remote desktop into the machine, says domain controller cannot be

> > reached for authentication (UserEnv error ID 1053 occurs in Application log)

> >

> > 2. DFS Replication stops (of course it cannot find either DC, one of which

> > it replicates to Event ID 5002)

> >

> > 3. Local workstations can access files, remote workstations that need to

> > authenticate to acces files cannot

> >

> > 4. Not able to connect to internet through IE. IP configuration is correct

> > on NIC card.

> >

> > 5. Recieve LSASRV error in system log, Event ID 40960 and NETLOGON error,

> > Event ID 5719.

> >

> > There are no scheduled (anything) that corrosponds with the timing of this,

> > and all processes, CPU, and memory seem normal. There are no additional error

> > messages as to why this happens and all hardware seems to be working

> > properly. A restart will fix this for the three week period.

> >

> > The only software installed is Veritas backup Exec Agent (which works

> > normally), Veritas Continious Protection Server Agent (which quits working),

> > and Trend Micro Client (set to scan in off hours, no real time scans) There

> > is no known malware or viruses present on the system.

> >

> > The Server is a Dell NX1950 with a MD3000 Raid Enclosure. All Firmware,

> > Bios, and MS patches are updated. If anyone has a clue as to what may be

> > causing this, or if you need more information, let me know. We have been

> > having this problem since October, and the Tech support at Dell does not seem

> > to be able to figure it out either.

> >

> > --

> > To invent, you need a good imagination and a pile of junk.

> > Thomas A. Edison (1847 - 1931)

> >