untrusted domain VPN

[Haploe79]

I have a simple VPN setup to the internal network which has 2 subnets, both of which are connected to the VPN server. The problem I have is that anyone vpn'ing in from a machine that is a member of the domain can access dns, exchange, everything. If a computer that isn't part of the domain connects even with a domain user account, they can't.

In client-side vpn properties I can put the domain suffix, which then lets me access dns server for queries, but still can't access exchange through outlook. It always asks me for credentials, and none given will ever work.

I have a feeling this is a common problem, and I hope someone has found a work around that doesn't require me to add everybody's personal computer to my domain.

 

[ktechit]

I am having same problem as you. NT Domain, with some W2K servers on the LAN. Outsourcing computers that try to come into the LAN via the VPN router connect ok, but cannot really logon to the domain in any way. The remote pc's are WinXP Pro. I am having them test the basics:
1- Ping test to a couple of server addresses
2- Ping test to same servers by name
3- add entries to hosts and lmhosts, referencing the server addresses and domain name ( i.e. #pre #dom:domain)
4- In some NT 4 domains there is a scope ID that needs to be hardcoded in registry in order to communicate in that domain, mainly W2K and XP Pro machines - will try this also.
5- Put Wins entries in the remote machines, pointing to wins servers on the LAN.
Hope this helps - I will post after we try these items ourselves.