Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- From: "Michael Giorgio - MS MVP" <Michael.Giorgio@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 3 Aug 2006 12:59:31 -0400
As long as you do know this should be handled by DNS...
Your remote name table is missing the domain name 1b
unique name for domains. Mostlikely cause is an incorrect
domain name 1b entry in lmhosts. You have to make sure
there are 15 characters in the domain name by adding spaces
after your NetBIOS domain name to make up 15 spaces or
the 1b name won't be cached e.g.,:
DC IP x.x.x.x "DomainBNAME----\0x1b" #PRE
I used hyphens in place of spaces so you could see the four
spaces needed to complete the domain name. The actual
NetBIOS name of domainB plus enough spaces to add up
to 15 will cure add the 1b name into the cache. Although I
doubt this will cure your issue it will remove NetBIOS name
resolution from one your possible causes..
<newsgroups.jd@xxxxxxxxx> wrote in message news:
Michael,
Thank you for the response, getting another set of eyes before I call
MS is always helpful. I had already verifed the LMHOST lookup was
enabled, but double checked again and it was. Here is the result from
the nbtstat on both DCs
Local Area Connection:
Node IpAddress: [x.x.156.151] Scope Id: [] - DOMAIN A
NetBIOS Remote Cache Name Table
Name Type Host Address Life [sec]
------------------------------------------------------------
Domain B DC <03> UNIQUE x.x.6.67 -1
Domain B DC <00> UNIQUE x.x.6.67 -1
Domain B DC <20> UNIQUE x.x.6.67 -1
Domain B <1C> GROUP x.x.6.67 -1
Domain B.... <03> UNIQUE x.x.6.67 -1
Domain B.... <00> UNIQUE x.x.6.67 -1
Domain B.... <20> UNIQUE x.x.6.67 -1
Local Area Connection 2:
Node IpAddress: [x.x.6.67] Scope Id: [] - DOMAIN B
NetBIOS Remote Cache Name Table
Name Type Host Address Life [sec]
------------------------------------------------------------
DOMAIN A <1C> GROUP x.x.156.151 -1
DOMAIN A... <03> UNIQUE x.x.156.151 -1
DOMAIN A... <00> UNIQUE x.x.156.151 -1
DOMAIN A... <20> UNIQUE x.x.156.151 -1
Domain A DC <03> UNIQUE x.x.156.151 -1
Domain A DC <00> UNIQUE x.x.156.151 -1
Domain A DC <20> UNIQUE x.x.156.151 -1
As for secondary domain - are you refering to a secondary DNS zone? I
had never heard it refered to as a secondary domain? but again - the
name resolution seems to be functioning, which is why I am baffled....
JD
Michael Giorgio - MS MVP wrote:
Try adding them as secondary domains and see if this resolves
your issue.. W2k or higher uses DNS for this type of connectivity.
NetBIOS which use WINS or lmhosts is necessary in NT 4.0.
Well to be sure your lmhosts are configured properly you have to
make sure the adapters are configured for NetBIOS and lmhosts
lookup. Open a dos prompt on each machine and run nbtstat -c
and post the results. You can mask the names and tcp/ip addresses.
.
- Follow-Ups:
- Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- From: newsgroups . jd
- Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- References:
- No logon server available - Windows 2003 Trust Issue? NS Issue?
- From: newsgroups . jd
- Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- From: Michael Giorgio - MS MVP
- Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- From: newsgroups . jd
- Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- From: Michael Giorgio - MS MVP
- Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- From: newsgroups . jd
- No logon server available - Windows 2003 Trust Issue? NS Issue?
- Prev by Date: Re: Cannot open port 80 for http access
- Next by Date: DNS Problems
- Previous by thread: Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- Next by thread: Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
- Index(es):
Relevant Pages
|
