Server 2003 VPN blocking access to non-domain machines

I'm running a Windows Server 2003 machine at the office that's acting
as a VPN and also provides a backup for Active Directory, DNS, and
DHCP.

For some reason, however, when I'm connected to the VPN, I can't access
any of the machines on the remote network that aren't a part of the
domain to which I authenticated. And by access, I mean simple stuff
like pinging them or trying to hit web servers that are being hosted on
them - nothing that should actually require domain level
authentication.

When I'm at the office on the local LAN, all that stuff works fine. If,
from home, I terminal into a domain authenticated machine on the remote
network, I can then ping the non-domain machines from there.

So, the following works: Home -> VPN -> Remote Domain Authenticated
Machine -> Non-Domain Machine

And this does not: Home -> VPN -> Non-Domain Machine

I've been trying to figure this out all day and am stumped. Any ideas?
I have added the machine to DNS and the name resolves (I get the right
IP address returned to me), but no traffic is being allowed through to
that IP. Is there something in the VPN setup that would restrict
access to only those machines in WINS or in AD? If so, is there a way
to disable that?

Thanks for any help on this!

-- Trav

Making a VPN connection is not the same thing as doing a domain logon.
All that it does is set up an IP connection. If you want to actually do a
domain login, set the client to the "logon using a dialup connection"
option.

If you do a local login at home, then set up a VPN to the office, the
credentials you are using are those of your local login, not your domain
login.

(E-Mail Removed) wrote:
> I'm running a Windows Server 2003 machine at the office that's acting
> as a VPN and also provides a backup for Active Directory, DNS, and
> DHCP.
>
> For some reason, however, when I'm connected to the VPN, I can't
> access any of the machines on the remote network that aren't a part
> of the domain to which I authenticated. And by access, I mean simple
> stuff like pinging them or trying to hit web servers that are being
> hosted on them - nothing that should actually require domain level
> authentication.
>
> When I'm at the office on the local LAN, all that stuff works fine.
> If, from home, I terminal into a domain authenticated machine on the
> remote network, I can then ping the non-domain machines from there.
>
> So, the following works: Home -> VPN -> Remote Domain Authenticated
> Machine -> Non-Domain Machine
>
> And this does not: Home -> VPN -> Non-Domain Machine
>
> I've been trying to figure this out all day and am stumped. Any ideas?
> I have added the machine to DNS and the name resolves (I get the right
> IP address returned to me), but no traffic is being allowed through to
> that IP. Is there something in the VPN setup that would restrict
> access to only those machines in WINS or in AD? If so, is there a way
> to disable that?
>
> Thanks for any help on this!
>
> -- Trav