Help - Intermittent logon problems

I have some intermittent logon problems. The network consists of 20 WS
running XP pro, Server running W2003, All machine are on a hub that is
uplinked to DSL router which is configured for DHCP for all machines.

Users are defined in AD as domain admins for now. I can logon to the domain
at times and other times I cannot. Event log on the WS side give me 1054 and
15 errors.

Event log on Server side give me 6702 and 8003 errors.

Could this be because all machine have Dynamic ip's instead of static ip's,
I would really appreciate any help on this problem.

SM

In news:(E-Mail Removed),
SM <(E-Mail Removed)> posted a question
Then Kevin replied below:
> I have some intermittent logon problems. The network
> consists of 20 WS running XP pro, Server running W2003,
> All machine are on a hub that is uplinked to DSL router
> which is configured for DHCP for all machines.
>
> Users are defined in AD as domain admins for now. I can
> logon to the domain at times and other times I cannot.
> Event log on the WS side give me 1054 and 15 errors.
>
> Event log on Server side give me 6702 and 8003 errors.
>
> Could this be because all machine have Dynamic ip's
> instead of static ip's, I would really appreciate any
> help on this problem.

All machines? Including the DC?
If your DC is dynamic that is a big part of the problem, it must be static
with DNS installed an _ALL_ machine _MUST_ use its address for DNS
_ONLY_.(Including the DC)

Chances are, since you are using your router for DHCP it is giving out your
ISP's DNS, you really should disable DHCP on the Router and enable DHCP on
the Win2k3 with options 003 006 and 015. Make sure option 006 is giving the
DCs address for DNS.

You can configure your router or your ISP's DNS as a forwarder for your DNS
server. Instructions for setting up DNS for internet access are in the
following KB article.
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default...b;en-us;825036

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
http://support.microsoft.com/default...b;en-us;323380

828731 - An External DNS Query May Cause an Error Message in Windows Server
2003
http://support.microsoft.com/default...b;en-us;828731

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your
issue. To respond directly to me remove the nospam. from my
email. ==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

I have configured all machines with static ip's. The primary DNS is the ip
of the 2003 server, secondary DNS is my ISP's DNS. My gateway is the ip of
the switch. Everything seems to be working well except for this one machine
that does not see the Server.

When I look at the log of the problematic client machine this is what I see:
(orange being the domain name)

"The domain name orange might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.
DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain orange:
The query was for the SRV record for _ldap._tcp.dc._msdcs.orange
The following domain controllers were identified by the query:
mths-server1.orange
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or
are not running."

Any help would be appreciated, Thank you.

SM

"Kevin D. Goodknecht Sr. [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In news:(E-Mail Removed),
> SM <(E-Mail Removed)> posted a question
> Then Kevin replied below:
> > I have some intermittent logon problems. The network
> > consists of 20 WS running XP pro, Server running W2003,
> > All machine are on a hub that is uplinked to DSL router
> > which is configured for DHCP for all machines.
> >
> > Users are defined in AD as domain admins for now. I can
> > logon to the domain at times and other times I cannot.
> > Event log on the WS side give me 1054 and 15 errors.
> >
> > Event log on Server side give me 6702 and 8003 errors.
> >
> > Could this be because all machine have Dynamic ip's
> > instead of static ip's, I would really appreciate any
> > help on this problem.
>
> All machines? Including the DC?
> If your DC is dynamic that is a big part of the problem, it must be static
> with DNS installed an _ALL_ machine _MUST_ use its address for DNS
> _ONLY_.(Including the DC)
>
> Chances are, since you are using your router for DHCP it is giving out
your
> ISP's DNS, you really should disable DHCP on the Router and enable DHCP on
> the Win2k3 with options 003 006 and 015. Make sure option 006 is giving
the
> DCs address for DNS.
>
> You can configure your router or your ISP's DNS as a forwarder for your
DNS
> server. Instructions for setting up DNS for internet access are in the
> following KB article.
> 825036 - Best practices for DNS client settings in Windows 2000 Server and
> in Windows Server 2003
> http://support.microsoft.com/default...b;en-us;825036
>
> 323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
> http://support.microsoft.com/default...b;en-us;323380
>
> 828731 - An External DNS Query May Cause an Error Message in Windows
Server
> 2003
> http://support.microsoft.com/default...b;en-us;828731
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ============================
> --
> When responding to posts, please "Reply to Group" via your
> newsreader so that others may learn and benefit from your
> issue. To respond directly to me remove the nospam. from my
> email. ==========================================
> http://www.lonestaramerica.com/
> ==========================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ==========================================
> Keep a back up of your OE settings and folders with
> OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ==========================================
>
>

In news:%(E-Mail Removed),
SM <(E-Mail Removed)> posted a question
Then Kevin replied below:
> I have configured all machines with static ip's. The
> primary DNS is the ip of the 2003 server, secondary DNS
> is my ISP's DNS. My gateway is the ip of the switch.
> Everything seems to be working well except for this one
> machine that does not see the Server.
>
> When I look at the log of the problematic client machine
> this is what I see: (orange being the domain name)
>
> "The domain name orange might be a NetBIOS domain name.
> If this is the case, verify that the domain name is
> properly registered with WINS.
> If you are certain that the name is not a NetBIOS domain
> name, then the following information can help you
> troubleshoot your DNS configuration.
> DNS was successfully queried for the service location
> (SRV) resource record used to locate a domain controller
> for domain orange:
> The query was for the SRV record for
> _ldap._tcp.dc._msdcs.orange
> The following domain controllers were identified by the
> query: mths-server1.orange
> Common causes of this error include:
> - Host (A) records that map the name of the domain
> controller to its IP addresses are missing or contain
> incorrect addresses. - Domain controllers registered in
> DNS are not connected to the network or are not running."
>
> Any help would be appreciated, Thank you.
>

You have more problems than you know of, if "orange" is your domain name, it
is a single-label domain name. This causes many problems with Active
Directory and DNS because it does not have a hierarchy to follow. That is
the reason it is giving you the error about it being a NetBIOS name. When
you DCPROMOed the server it popped up with a warning about the single-label
DNS name, apparently you chose to ignore the warning.
You should take steps to rename this domain now (an option added in Win2k3)
and give it a multi-label DNS name such as orange.local.
Additionally, you cannot use your ISP's DNS in _ANY_ position on _ANY_
member of an AD Domain, including the server DNS is on and the DC. The only
place you can use your ISP's DNS is as a forwarder in the properties of DNS
of the DNS service.

826743 - Clients cannot dynamically register DNS records in a single-label
forward lookup zone: http://support.microsoft.com/?id=826743


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your
issue. To respond directly to me remove the nospam. from my
email. ==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================