client cant authenticate to domain if moved to different VPN locat

Here is the problem I am facing:
1: Build a new workstation and authenticate it to the domain localy (the DC
is local for me, but it doesnt matter)
2: Move the new workstation to a remote location connected by VPN. (The VPN
is set up by our routers, not by any client software)

When any users try to view the domain it will give them the old "cant
access/might not have rights" error.
I tried to take the user off the domain, then go back on, but the error
"domain inaccessable" came up. I had to remove Client for Microsoft Networks
in the lan settings just to get her back up for remote access.

Does anyone know what causes these kind of errors? Somone in a remote office
added a new computer to the domain, and had no problem, but then moved that
computer to the home office and the same thing happened.

"MillMaster" <(E-Mail Removed)> wrote in message
news:FF9C4FCF-6526-42A9-A6CA-(E-Mail Removed)...

> "domain inaccessable" came up. I had to remove Client for Microsoft
Networks
> in the lan settings just to get her back up for remote access.

Put that back the way it was.

> Does anyone know what causes these kind of errors? Somone in a remote
office
> added a new computer to the domain, and had no problem, but then moved
that
> computer to the home office and the same thing happened.

The VPN connection does not use the TCP/IP Settings of the NIC,...it uses
the TCP/IP Settings of the dial-up connectiod,...therefore the dialup
connectiod must include the DNS Server's IP# and also the same for WINS if
you use WINS.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The router maintains the VPN, the network is configured via the LAN and not
the dialup because of this. All the remote users are on the same subnet as
us, they just hit a different gateway.

Also, what do you think about forcing kerberos to use TCP instead of UDP?

"Phillip Windell" wrote:

> "MillMaster" <(E-Mail Removed)> wrote in message
> news:FF9C4FCF-6526-42A9-A6CA-(E-Mail Removed)...
>
> > "domain inaccessable" came up. I had to remove Client for Microsoft
> Networks
> > in the lan settings just to get her back up for remote access.
>
> Put that back the way it was.
>
> > Does anyone know what causes these kind of errors? Somone in a remote
> office
> > added a new computer to the domain, and had no problem, but then moved
> that
> > computer to the home office and the same thing happened.
>
> The VPN connection does not use the TCP/IP Settings of the NIC,...it uses
> the TCP/IP Settings of the dial-up connectiod,...therefore the dialup
> connectiod must include the DNS Server's IP# and also the same for WINS if
> you use WINS.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

"MillMaster" <(E-Mail Removed)> wrote in message
news:B4869E3F-4BDB-436B-90B6-(E-Mail Removed)...
> The router maintains the VPN, the network is configured via the LAN and
not
> the dialup because of this. All the remote users are on the same subnet as
> us, they just hit a different gateway.

VPN itself *is* a "dialup" technology. The "VPN Adapter" replaces what used
to be the modem,....the IP# of the VPN Router replaces what used to be the
phone number. You "dial" an IP# to establish a VPN connection. So, the
same answer as before:

The VPN connection does not use the TCP/IP Settings of the NIC,...it uses
the TCP/IP Settings of the dial-up connectiod,...therefore the dialup
connectiod must include the DNS Server's IP# and also the same for WINS if
you use WINS.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com