Topic: Real Windows Domain Login after VPN to sme server

[Chuck Wilson]

I can successfully vpn (pptp) to my sme server 5.1.2 from just about any kind of internet connection that exists.  Once this is complete I can browse netbios names in network neighborhood of all of the servers and computers in my domain.

When I try to access a domain controller or other server to trigger a domain login I receive one of two errors:

1.  No logon server was available to service your request - (this error occurs when I attempt it from a broadband connection behind a little cable router.

2.  No list of servers is available - (this occurs when I attempt to access a server after vpn'ing after a dialup ISP connection.

The whole network is Windows 2000 Server and Desktop.  The domain is mixed mode.  The client computers that I initiate the vpn from are already memebers of the domain (configured before they left the building).

I don't want to buy another Windows Server to serve as RRAS box.  My current Windows servers are busy enough and I don't want to add services to them.  I just want to map drives to two server shares over the sme vpn.  These drives are normally mapped via kix script for computers that are on the LAN in the building.

Does the sme server need to be a member of the domain?  Am I missing a Samba thing I don't understand?  All network services are handled by Windows servers internally: DHCP, Wins, etc....  Does the sme server need to be a DC?  Will it hurt my current network setup to configure the sme server as a DC?

Any help would be greatly appreciated.  I have searched and searched other posts.  I found some posts that are similar but it seems these posters do not have a true Windows domain behind sme.  Any help?

Regards and Thanks

Chuck

[Pete Anderson]

Try using an lmhosts file that indicates the ip address of the domain controller.

> (EXAMPLE)
> Your domain name is "Globe", your PDC NetBIOS name is "Mongo", and you
have other various backup domain controllers. Your LMHOSTS file would look
like this:
>
> 199.199.199.1        mongo          #PRE #DOM:globe
> 199.199.199.1        "globe \0x1b"   #PRE
> 199.199.199.2        otherdc1       #PRE #DOM:globe
> 199.199.199.3        otherdc2       #PRE #DOM:globe
>
>
> The first entry allows the PDC to act as a logon domain controller for the
client,
>  the second entry allows the client browser service to explicitly find the
PDC.
> Remember you will probably have multiple lines similar to the first line
(for multiple domain controllers),
> but only one line with the \0x1b directive (to designate the PDC).
> Note that the domain name must be in quotes, and padded with spaces for a
total of 15 characters before the \0x1b portion.
> (The example above shows commas for visual placeholders, however in a real
LMHOSTS file these commas would be replaced with spaces).
> Also be aware that moving the PDC role to another Windows NT Server (via
promotion) will cause your \0x1b entry to be invalid. Options to fix this: