"No Domain Controller available" problems with VPN

[Newsguy]

Not sure if this is the right place for this question but I think you folks
might know the answer. I'm running an XP Pro client, across a vpn using
linksys routers. My office is a Windows network with a Windows 2003 SBS
server acting as the PDC/Wins/AD server.

I was able to successfully join the domain on the XP machine. But now, I've
got a wierd issue.

I appear to be authenticating with cached credentials, and then, when I try
to open a share (note: scripted mappings don't work), I ultimately get told
that no domain controller was available to authenticate me. Interestingly,
an exchange/outlook connection works fine, and it of course requires
authentication as well, though in a similar but different manner.

I am getting wins name resolution because I can ping the server in question
by name.

Any ideas?

Tim

 

[Newsguy]

I should add that I've also discovered that I do not get a 1b record from
WINS, only a 1c. LMHOSTS didn't fix it.

 

[Lanwench [MVP - Exchange]]

Since you mentioned LMHOSTS - are you *sure* WINS is working across the
connection?

FWIW, your LMHOSTS file entry for the 0x1b needs to be properly entered with
the "padding spaces" as per MSKB 180094

If you do nbtstat -R, and then nbtstat -c, do you see the 1b entry for the
domain?

 

[Guest]

If the client machine is XP. Are the XP using DNS resolution? It´s DNS server must be a server that hosts the AD domain zone probably a domain controler.

 

[Bahjah]

Well, I'm using lmhosts as a tool here to find the problem. I'll check the
spaces and see if that's the problem. But assuming that works, it still
doesn't explain why Wins isn't providing the DC to me.

"Lanwench [MVP - Exchange]"

 

[Bahjah]

The XP Pro client is pointing to the 2003 SBS (AD Host) server for both WINS
and DNS.

Thanks for your assistance

Tim

If the client machine is XP. Are the XP using DNS resolution? It´s DNS

server must be a server that hosts the AD domain zone probably a domain
controler.

 

[Bahjah]

Sorry, just noticed the different name, I'm Newsguy, and Bahjah, two
different ISP accounts, so y'all don't get confused.

 

[Bahjah]

For what's it worth, I did have a "space" error on the 1b record in lmhosts.
Resolving that seems to have fixed the problem, but I still would like to
know why WINS won't resolve the 1b record for me.

Tim

 

[Lanwench [MVP - Exchange]]

Did you check your WINS server to make sure it included option 44 (from
memory) - hybrid mode?

 

[Marina Roos]

Update your memory Lanwench ( ;-) ). 044 is pointing to the server-IP, 046
(0x8) is that hybrid broadcast thing.

--
Regards,

Marina

"Lanwench [MVP - Exchange]"

 

[Lanwench [MVP - Exchange]]

<blushes> It's been a while. I do need a memory upgrade.

Update your memory Lanwench ( ;-) ). 044 is pointing to the
server-IP, 046 (0x8) is that hybrid broadcast thing.


"Lanwench [MVP - Exchange]"

Did you check your WINS server to make sure it included option 44
(from memory) - hybrid mode?

 

[Bahjah]

Ok, that seemed to fix that problem. Thanks for the help with that. I have
a new issue though if you don't mind.

I can now log in and get authenticated fine, but the login in process is
taking FOREVER. Like 45 seconds to log in. Is there anything I can do to
speed this up.

Thanks,

Tim

"Lanwench [MVP - Exchange]"

<blushes> It's been a while. I do need a memory upgrade.

Update your memory Lanwench ( ;-) ). 044 is pointing to the
server-IP, 046 (0x8) is that hybrid broadcast thing.


"Lanwench [MVP - Exchange]"

Did you check your WINS server to make sure it included option 44
(from memory) - hybrid mode?

Bahjah wrote:
For what's it worth, I did have a "space" error on the 1b record in
lmhosts. Resolving that seems to have fixed the problem, but I still
would like to know why WINS won't resolve the 1b record for me.

Tim

The XP Pro client is pointing to the 2003 SBS (AD Host) server for
both WINS and DNS.

Thanks for your assistance

Tim

If the client machine is XP. Are the XP using DNS resolution? It´s
DNS
server must be a server that hosts the AD domain zone probably a
domain controler.

 

[Marina Roos]

Check the ipconfig/all on the client. Does everything point to the server?

--
Regards,

Marina

Ok, that seemed to fix that problem. Thanks for the help with that. I have
a new issue though if you don't mind.

I can now log in and get authenticated fine, but the login in process is
taking FOREVER. Like 45 seconds to log in. Is there anything I can do to
speed this up.

Thanks,

Tim

"Lanwench [MVP - Exchange]"

<blushes> It's been a while. I do need a memory upgrade.

Update your memory Lanwench ( ;-) ). 044 is pointing to the
server-IP, 046 (0x8) is that hybrid broadcast thing.


"Lanwench [MVP - Exchange]"
<[email protected]> schreef in
bericht Did you check your WINS server to make sure it included option 44
(from memory) - hybrid mode?

Bahjah wrote:
For what's it worth, I did have a "space" error on the 1b record in
lmhosts. Resolving that seems to have fixed the problem, but I still
would like to know why WINS won't resolve the 1b record for me.

Tim

The XP Pro client is pointing to the 2003 SBS (AD Host) server for
both WINS and DNS.

Thanks for your assistance

Tim

If the client machine is XP. Are the XP using DNS resolution? It´s
DNS
server must be a server that hosts the AD domain zone probably a
domain controler.

 

[Bahjah]

not the default gateway, but other than that, yes, dns and wins.

Check the ipconfig/all on the client. Does everything point to the server?

--
Regards,

Marina

Ok, that seemed to fix that problem. Thanks for the help with that. I have
a new issue though if you don't mind.

I can now log in and get authenticated fine, but the login in process is
taking FOREVER. Like 45 seconds to log in. Is there anything I can do to
speed this up.

Thanks,

Tim

"Lanwench [MVP - Exchange]"

<blushes> It's been a while. I do need a memory upgrade.

Marina Roos wrote:
Update your memory Lanwench ( ;-) ). 044 is pointing to the
server-IP, 046 (0x8) is that hybrid broadcast thing.


"Lanwench [MVP - Exchange]"
<[email protected]> schreef in
bericht Did you check your WINS server to make sure it included option 44
(from memory) - hybrid mode?

Bahjah wrote:
For what's it worth, I did have a "space" error on the 1b record in
lmhosts. Resolving that seems to have fixed the problem, but I still
would like to know why WINS won't resolve the 1b record for me.

Tim

The XP Pro client is pointing to the 2003 SBS (AD Host) server for
both WINS and DNS.

Thanks for your assistance

Tim

If the client machine is XP. Are the XP using DNS resolution? It´s
DNS
server must be a server that hosts the AD domain zone probably a
domain controler.

 

[Marina Roos]

Does the server only have 1 nic?
BTW: 45 seconds when connecting over VPN is not that much.

--
Regards,

Marina

not the default gateway, but other than that, yes, dns and wins.

Check the ipconfig/all on the client. Does everything point to the server?

--
Regards,

Marina

I
have

do

to

speed this up.

Thanks,

Tim

"Lanwench [MVP - Exchange]"
<blushes> It's been a while. I do need a memory upgrade.

Marina Roos wrote:
Update your memory Lanwench ( ;-) ). 044 is pointing to the
server-IP, 046 (0x8) is that hybrid broadcast thing.


"Lanwench [MVP - Exchange]"
<[email protected]>

schreef

in

 

[Bahjah]

Changing the node type was the answer. If it uses WINS instead of
broadcasting first, much faster, down to like 12 seconds. LMHOSTS is even
faster.

Tim

Does the server only have 1 nic?
BTW: 45 seconds when connecting over VPN is not that much.

--
Regards,

Marina

not the default gateway, but other than that, yes, dns and wins.

process

is

taking FOREVER. Like 45 seconds to log in. Is there anything I can

do

to
speed this up.

Thanks,

Tim

"Lanwench [MVP - Exchange]"
message
<blushes> It's been a while. I do need a memory upgrade.

Marina Roos wrote:
Update your memory Lanwench ( ;-) ). 044 is pointing to the
server-IP, 046 (0x8) is that hybrid broadcast thing.


"Lanwench [MVP - Exchange]"
<[email protected]>

schreef

in
bericht Did you check your WINS server to make sure it included option 44
(from memory) - hybrid mode?

Bahjah wrote:
For what's it worth, I did have a "space" error on the 1b

record
in

lmhosts. Resolving that seems to have fixed the problem, but I still
would like to know why WINS won't resolve the 1b record for me.

Tim

The XP Pro client is pointing to the 2003 SBS (AD Host)

server
for

both WINS and DNS.

Thanks for your assistance

Tim

If the client machine is XP. Are the XP using DNS

resolution?
It´s

DNS
server must be a server that hosts the AD domain zone

probably

a