No domain server was available
 

On a Compaq Deskpro EX C733 PC an "No domain server was available to validate your password" error message is generated when a user tries to log on to the Microsoft network. The PC is running Windows 98 SE, all TCP/IP properties are default (dynamic), the client for Windows networking "log on to domain" is checked, the connection is established remotely via a VPN client (Cisco). At start-up the login is cancelled, the VPN client is started and it triggers a Network login screen where username, password and domain name are entered. Then the error message occurs.
The VPN connection itself succeeds and it is possible to map a network drive manually, but of course no server side login script is executed.

On an other machine (a very old Tulip) under exactly the same software and connection conditions (same DSL connection, same client side SMC router, even same cable, same user, same password), no error message is generated, the login is working fine, the login script is executed as expected.
So, apparently it's a client side problem.
How can I troubleshoot the Compaq?
Thanks

Leo Leys

No domain server was available
 

-----Original Message-----

So, apparently it's a client side problem.
How can I troubleshoot the Compaq?
Thanks

A few ideas:
1) I suspect it's a WINS or DNS problem - the Compaq cannot
resolve the address of the domain it's trying to log on to.
Have you got a "hosts" or "hosts.sam" file on the Tulip
machine? If so, copy it to the Compaq. Otherwise, check the
DNS & WINS settings very carefuly for discrepancies between
the two PC's setups.
2) Clutching at straws time :-)
Are the local (presumably NAT) IP addresses of the two PCs
the same? If not, try making the Compaq the same as the Tulip.

No domain server was available
 

Thanks for your ideas
1. WINS and DNS are both disabled on both PC's
2. the hosts.sam files are identidcal on both PC's.
The Compaq still cant't log on, the Tulip can..
Leo Leys
wrote in message
...

-----Original Message-----

So, apparently it's a client side problem.
How can I troubleshoot the Compaq?
Thanks

A few ideas:
1) I suspect it's a WINS or DNS problem - the Compaq cannot
resolve the address of the domain it's trying to log on to.
Have you got a "hosts" or "hosts.sam" file on the Tulip
machine? If so, copy it to the Compaq. Otherwise, check the
DNS & WINS settings very carefuly for discrepancies between
the two PC's setups.
2) Clutching at straws time :-)
Are the local (presumably NAT) IP addresses of the two PCs
the same? If not, try making the Compaq the same as the Tulip.

No domain server was available
 

Thanks for the ideas. But:
1. Both Wins and DNS are the same on both machines (they are disabled)
2. On both machines the hosts.sam files are the same.

The Compaq still doesn't log on, the Tulip does.
The problem isn't resolved yet...
Leo Leys


" wrote:


-----Original Message-----

So, apparently it's a client side problem.
How can I troubleshoot the Compaq?
Thanks

A few ideas:
1) I suspect it's a WINS or DNS problem - the Compaq cannot
resolve the address of the domain it's trying to log on to.
Have you got a "hosts" or "hosts.sam" file on the Tulip
machine? If so, copy it to the Compaq. Otherwise, check the
DNS & WINS settings very carefuly for discrepancies between
the two PC's setups.
2) Clutching at straws time :-)
Are the local (presumably NAT) IP addresses of the two PCs
the same? If not, try making the Compaq the same as the Tulip.

No domain server was available
 

1. The WINS and DNS were both disabled on both PC's
2. The hosts.sam files on both machines are identical.

The Compaq still can't log on, the Tulip does...

Leo Leys

" wrote:


-----Original Message-----

So, apparently it's a client side problem.
How can I troubleshoot the Compaq?
Thanks

A few ideas:
1) I suspect it's a WINS or DNS problem - the Compaq cannot
resolve the address of the domain it's trying to log on to.
Have you got a "hosts" or "hosts.sam" file on the Tulip
machine? If so, copy it to the Compaq. Otherwise, check the
DNS & WINS settings very carefuly for discrepancies between
the two PC's setups.
2) Clutching at straws time :-)
Are the local (presumably NAT) IP addresses of the two PCs
the same? If not, try making the Compaq the same as the Tulip.