No logon server available - Windows 2003 Trust Issue? NS Issue?

THanks for any input ahead of time...

I have 2 - Windows 2003 R2 Domains with a two way trust set up.

Domain A

Windows Firewall - turned off
LMHOST Entries

DC IP x.x.x.x DCHostName #PRE #DOM: "DomainBName
DC IP x.x.x.x "DomainBNAME \0x1b" #PRE


Domain B

Windows Firewall - turned off
LMHOST Entries

DC IP x.x.x.x DCHostName #PRE #DOM: "DomainAName
DC IP x.x.x.x "DomainANAME \0x1b" #PRE


Trust created fine

Domain A tries to access shared folder on Domain B - I get auth box
- which is good. Once I assign NTFS and Share permissions, that will
go away.


Domain B tries to access shared folder on Domain A - I get following

<error>

\\dcname\test is not accessible. You might not have permission to use
this network
resource. Contact the administrator of this server to find out if you
have access
permissions.

There are currently no logon servers available to service this logon
request.

</error>

I have read alot of Q articles and alot of post regarding this error,
and it mostly relates to name resolution. I have verified my entries
on both domain controllers. I can ping back and forth using wins name.
I have added DC entries in WINS just to make sure... shouldn't have
to if they are in lmhost.

I have run nslookup on both servers to verify what it sees as the name
server for each domain.

I cant see to figure out what is going on - I ran a sniff on the port
for DC B while trying to access DC A and do not see anything out of the
ordinary...

Any thoughts?

Since these are W2k3 domains you should be able to use DNS
to get them communicating properly. Add the remote DNS servers
as secondary DNS servers on each W2k3 DC.
<(E-Mail Removed)> wrote in message news:
> THanks for any input ahead of time...
>
> I have 2 - Windows 2003 R2 Domains with a two way trust set up.
>
> Domain A
>
> Windows Firewall - turned off
> LMHOST Entries
>
> DC IP x.x.x.x DCHostName #PRE #DOM: "DomainBName
> DC IP x.x.x.x "DomainBNAME \0x1b" #PRE
>
>
> Domain B
>
> Windows Firewall - turned off
> LMHOST Entries
>
> DC IP x.x.x.x DCHostName #PRE #DOM: "DomainAName
> DC IP x.x.x.x "DomainANAME \0x1b" #PRE
>
>
> Trust created fine
>
> Domain A tries to access shared folder on Domain B - I get auth box
> - which is good. Once I assign NTFS and Share permissions, that will
> go away.
>
>
> Domain B tries to access shared folder on Domain A - I get following
>
> <error>
>
> \\dcname\test is not accessible. You might not have permission to use
> this network
> resource. Contact the administrator of this server to find out if you
> have access
> permissions.
>
> There are currently no logon servers available to service this logon
> request.
>
> </error>
>
> I have read alot of Q articles and alot of post regarding this error,
> and it mostly relates to name resolution. I have verified my entries
> on both domain controllers. I can ping back and forth using wins name.
> I have added DC entries in WINS just to make sure... shouldn't have
> to if they are in lmhost.
>
> I have run nslookup on both servers to verify what it sees as the name
> server for each domain.
>
> I cant see to figure out what is going on - I ran a sniff on the port
> for DC B while trying to access DC A and do not see anything out of the
> ordinary...
>
> Any thoughts?
>

For DNS - I actually created a conditional forwarder on each domain -
which also seems to be working fine -

>From each domain I am able to ping or at least resolve names on each
side with either FQDNs or with netbios names....

I did this before...

So still getting the error

JD



Michael Giorgio - MS MVP wrote:
> Since these are W2k3 domains you should be able to use DNS
> to get them communicating properly. Add the remote DNS servers
> as secondary DNS servers on each W2k3 DC.
> <(E-Mail Removed)> wrote in message news:
> > THanks for any input ahead of time...
> >
> > I have 2 - Windows 2003 R2 Domains with a two way trust set up.
> >
> > Domain A
> >
> > Windows Firewall - turned off
> > LMHOST Entries
> >
> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainBName
> > DC IP x.x.x.x "DomainBNAME \0x1b" #PRE
> >
> >
> > Domain B
> >
> > Windows Firewall - turned off
> > LMHOST Entries
> >
> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainAName
> > DC IP x.x.x.x "DomainANAME \0x1b" #PRE
> >
> >
> > Trust created fine
> >
> > Domain A tries to access shared folder on Domain B - I get auth box
> > - which is good. Once I assign NTFS and Share permissions, that will
> > go away.
> >
> >
> > Domain B tries to access shared folder on Domain A - I get following
> >
> > <error>
> >
> > \\dcname\test is not accessible. You might not have permission to use
> > this network
> > resource. Contact the administrator of this server to find out if you
> > have access
> > permissions.
> >
> > There are currently no logon servers available to service this logon
> > request.
> >
> > </error>
> >
> > I have read alot of Q articles and alot of post regarding this error,
> > and it mostly relates to name resolution. I have verified my entries
> > on both domain controllers. I can ping back and forth using wins name.
> > I have added DC entries in WINS just to make sure... shouldn't have
> > to if they are in lmhost.
> >
> > I have run nslookup on both servers to verify what it sees as the name
> > server for each domain.
> >
> > I cant see to figure out what is going on - I ran a sniff on the port
> > for DC B while trying to access DC A and do not see anything out of the
> > ordinary...
> >
> > Any thoughts?
> >

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.

<(E-Mail Removed)> wrote in message news:
> For DNS - I actually created a conditional forwarder on each domain -
> which also seems to be working fine -
>
>>From each domain I am able to ping or at least resolve names on each
> side with either FQDNs or with netbios names....
>
> I did this before...
>
> So still getting the error
>
> JD
>
>
>
> Michael Giorgio - MS MVP wrote:
>> Since these are W2k3 domains you should be able to use DNS
>> to get them communicating properly. Add the remote DNS servers
>> as secondary DNS servers on each W2k3 DC.
>> <(E-Mail Removed)> wrote in message news:
>> > THanks for any input ahead of time...
>> >
>> > I have 2 - Windows 2003 R2 Domains with a two way trust set up.
>> >
>> > Domain A
>> >
>> > Windows Firewall - turned off
>> > LMHOST Entries
>> >
>> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainBName
>> > DC IP x.x.x.x "DomainBNAME \0x1b" #PRE
>> >
>> >
>> > Domain B
>> >
>> > Windows Firewall - turned off
>> > LMHOST Entries
>> >
>> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainAName
>> > DC IP x.x.x.x "DomainANAME \0x1b" #PRE
>> >
>> >
>> > Trust created fine
>> >
>> > Domain A tries to access shared folder on Domain B - I get auth box
>> > - which is good. Once I assign NTFS and Share permissions, that will
>> > go away.
>> >
>> >
>> > Domain B tries to access shared folder on Domain A - I get following
>> >
>> > <error>
>> >
>> > \\dcname\test is not accessible. You might not have permission to use
>> > this network
>> > resource. Contact the administrator of this server to find out if you
>> > have access
>> > permissions.
>> >
>> > There are currently no logon servers available to service this logon
>> > request.
>> >
>> > </error>
>> >
>> > I have read alot of Q articles and alot of post regarding this error,
>> > and it mostly relates to name resolution. I have verified my entries
>> > on both domain controllers. I can ping back and forth using wins name.
>> > I have added DC entries in WINS just to make sure... shouldn't have
>> > to if they are in lmhost.
>> >
>> > I have run nslookup on both servers to verify what it sees as the name
>> > server for each domain.
>> >
>> > I cant see to figure out what is going on - I ran a sniff on the port
>> > for DC B while trying to access DC A and do not see anything out of the
>> > ordinary...
>> >
>> > Any thoughts?
>> >
>

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.
>
> <(E-Mail Removed)> wrote in message news:
> > For DNS - I actually created a conditional forwarder on each domain -
> > which also seems to be working fine -
> >
> >>From each domain I am able to ping or at least resolve names on each
> > side with either FQDNs or with netbios names....
> >
> > I did this before...
> >
> > So still getting the error
> >
> > JD
> >
> >
> >
> > Michael Giorgio - MS MVP wrote:
> >> Since these are W2k3 domains you should be able to use DNS
> >> to get them communicating properly. Add the remote DNS servers
> >> as secondary DNS servers on each W2k3 DC.
> >> <(E-Mail Removed)> wrote in message news:
> >> > THanks for any input ahead of time...
> >> >
> >> > I have 2 - Windows 2003 R2 Domains with a two way trust set up.
> >> >
> >> > Domain A
> >> >
> >> > Windows Firewall - turned off
> >> > LMHOST Entries
> >> >
> >> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainBName
> >> > DC IP x.x.x.x "DomainBNAME \0x1b" #PRE
> >> >
> >> >
> >> > Domain B
> >> >
> >> > Windows Firewall - turned off
> >> > LMHOST Entries
> >> >
> >> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainAName
> >> > DC IP x.x.x.x "DomainANAME \0x1b" #PRE
> >> >
> >> >
> >> > Trust created fine
> >> >
> >> > Domain A tries to access shared folder on Domain B - I get auth box
> >> > - which is good. Once I assign NTFS and Share permissions, that will
> >> > go away.
> >> >
> >> >
> >> > Domain B tries to access shared folder on Domain A - I get following
> >> >
> >> > <error>
> >> >
> >> > \\dcname\test is not accessible. You might not have permission to use
> >> > this network
> >> > resource. Contact the administrator of this server to find out if you
> >> > have access
> >> > permissions.
> >> >
> >> > There are currently no logon servers available to service this logon
> >> > request.
> >> >
> >> > </error>
> >> >
> >> > I have read alot of Q articles and alot of post regarding this error,
> >> > and it mostly relates to name resolution. I have verified my entries
> >> > on both domain controllers. I can ping back and forth using wins name.
> >> > I have added DC entries in WINS just to make sure... shouldn't have
> >> > to if they are in lmhost.
> >> >
> >> > I have run nslookup on both servers to verify what it sees as the name
> >> > server for each domain.
> >> >
> >> > I cant see to figure out what is going on - I ran a sniff on the port
> >> > for DC B while trying to access DC A and do not see anything out of the
> >> > ordinary...
> >> >
> >> > Any thoughts?
> >> >
> >

More info -

Following error popped up a few times in Domain A -

<error>

This computer was not able to set up a secure session with a domain
controller in domain (Domain B) due to the following:
The remote procedure call failed and did not execute.
This may lead to authentication problems. Make sure that this computer
is connected to the network. If the problem persists, please contact
your domain administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it
sets up the secure session to the primary domain controller emulator in
the specified domain. Otherwise, this computer sets up the secure
session to any domain controller in the specified domain.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

</error>



(E-Mail Removed) wrote:
> 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.
> >
> > <(E-Mail Removed)> wrote in message news:
> > > For DNS - I actually created a conditional forwarder on each domain -
> > > which also seems to be working fine -
> > >
> > >>From each domain I am able to ping or at least resolve names on each
> > > side with either FQDNs or with netbios names....
> > >
> > > I did this before...
> > >
> > > So still getting the error
> > >
> > > JD
> > >
> > >
> > >
> > > Michael Giorgio - MS MVP wrote:
> > >> Since these are W2k3 domains you should be able to use DNS
> > >> to get them communicating properly. Add the remote DNS servers
> > >> as secondary DNS servers on each W2k3 DC.
> > >> <(E-Mail Removed)> wrote in message news:
> > >> > THanks for any input ahead of time...
> > >> >
> > >> > I have 2 - Windows 2003 R2 Domains with a two way trust set up.
> > >> >
> > >> > Domain A
> > >> >
> > >> > Windows Firewall - turned off
> > >> > LMHOST Entries
> > >> >
> > >> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainBName
> > >> > DC IP x.x.x.x "DomainBNAME \0x1b" #PRE
> > >> >
> > >> >
> > >> > Domain B
> > >> >
> > >> > Windows Firewall - turned off
> > >> > LMHOST Entries
> > >> >
> > >> > DC IP x.x.x.x DCHostName #PRE #DOM: "DomainAName
> > >> > DC IP x.x.x.x "DomainANAME \0x1b" #PRE
> > >> >
> > >> >
> > >> > Trust created fine
> > >> >
> > >> > Domain A tries to access shared folder on Domain B - I get auth box
> > >> > - which is good. Once I assign NTFS and Share permissions, that will
> > >> > go away.
> > >> >
> > >> >
> > >> > Domain B tries to access shared folder on Domain A - I get following
> > >> >
> > >> > <error>
> > >> >
> > >> > \\dcname\test is not accessible. You might not have permission to use
> > >> > this network
> > >> > resource. Contact the administrator of this server to find out if you
> > >> > have access
> > >> > permissions.
> > >> >
> > >> > There are currently no logon servers available to service this logon
> > >> > request.
> > >> >
> > >> > </error>
> > >> >
> > >> > I have read alot of Q articles and alot of post regarding this error,
> > >> > and it mostly relates to name resolution. I have verified my entries
> > >> > on both domain controllers. I can ping back and forth using wins name.
> > >> > I have added DC entries in WINS just to make sure... shouldn't have
> > >> > to if they are in lmhost.
> > >> >
> > >> > I have run nslookup on both servers to verify what it sees as the name
> > >> > server for each domain.
> > >> >
> > >> > I cant see to figure out what is going on - I ran a sniff on the port
> > >> > for DC B while trying to access DC A and do not see anything out of the
> > >> > ordinary...
> > >> >
> > >> > Any thoughts?
> > >> >
> > >

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..





<(E-Mail Removed)> 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.
>>

Good catch - after I tried this I did some searching and see you have
had to point this out to people more than once... I thought the
requirement was at least 15 characters... I actually had more than 15
in both and had to reduce it to be exactly 15 characters for it to
import the 1b record...

Anyways - I know have the ib recorbs showig up in nbtstat -c , but it
did not resolve the initial issue as you suspected...

JD




Michael Giorgio - MS MVP wrote:
> 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..
>
>
>
>
>
> <(E-Mail Removed)> 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.
> >>

Scratch that - after a reload I am getting auth boxes on both sides...
Thanks for your help!!

JD

> Good catch - after I tried this I did some searching and see you have
> had to point this out to people more than once... I thought the
> requirement was at least 15 characters... I actually had more than 15
> in both and had to reduce it to be exactly 15 characters for it to
> import the 1b record...
>
> Anyways - I know have the ib recorbs showig up in nbtstat -c , but it
> did not resolve the initial issue as you suspected...
>
> JD
>
>
>
>
> Michael Giorgio - MS MVP wrote:
> > 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..
> >
> >
> >
> >
> >
> > <(E-Mail Removed)> 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.
> > >>

Cool, Glad to hear you got it working and thank you
for the update. .. ;-)

<(E-Mail Removed)> wrote in message news:
> Scratch that - after a reload I am getting auth boxes on both sides...
> Thanks for your help!!
>