At home, and I am connected to my ISP via cable.

On home computer (Windows XP SP2) I created a PPTP VPN connection in Network
Connections, which I use to connect to company server. In TCP/IP properties
of the connection I've manually put DNS addresses of internal DNS servers. I
also checked "Use default gateway on remote network". I also put this
connection in first place in Advanced Settings-> Adapters and bindings.

When I connect to my company with this connection, it works, but all names
are still resolved with my ISP DNSs. Why is this happening, what have I
forgot? I need to, when I connect to my company with this connection, to use
internal DNS servers.

Do I have to change something on the server or on the client?

That should work. Have you also added the DNS suffix for your company to
the VPN client settings?

rem wrote:
> At home, and I am connected to my ISP via cable.
>
> On home computer (Windows XP SP2) I created a PPTP VPN connection in
> Network Connections, which I use to connect to company server. In
> TCP/IP properties of the connection I've manually put DNS addresses
> of internal DNS servers. I also checked "Use default gateway on
> remote network". I also put this connection in first place in
> Advanced Settings-> Adapters and bindings.
> When I connect to my company with this connection, it works, but all
> names are still resolved with my ISP DNSs. Why is this happening,
> what have I forgot? I need to, when I connect to my company with this
> connection, to use internal DNS servers.
>
> Do I have to change something on the server or on the client?

"Bill Grant" <not.available@online> wrote in message
news:OpwdFoG1GHA.1548@TK2MSFTNGP02.phx.gbl...
> That should work. Have you also added the DNS suffix for your company
> to the VPN client settings?


Yes, I also did that. (I forgot to mention). It still does not work.

We have the same situation. It's not been a problem, since our nurses
only use it to synchronize their laptops with a server and the server is
identified via an IP address.

I've found that adding a HOSTS file with the necessary definitions will
allow full name resolution....

Regards,
Hank Arnold

rem wrote:
> At home, and I am connected to my ISP via cable.
>
> On home computer (Windows XP SP2) I created a PPTP VPN connection in Network
> Connections, which I use to connect to company server. In TCP/IP properties
> of the connection I've manually put DNS addresses of internal DNS servers. I
> also checked "Use default gateway on remote network". I also put this
> connection in first place in Advanced Settings-> Adapters and bindings.
>
> When I connect to my company with this connection, it works, but all names
> are still resolved with my ISP DNSs. Why is this happening, what have I
> forgot? I need to, when I connect to my company with this connection, to use
> internal DNS servers.
>
> Do I have to change something on the server or on the client?
>
>
>

Today I tried to detect the packet flow.
I used two ethereals at the same time: one for VPN interface and one for
ethernet card interface(ISP via cable). Then I tried nslookup.

On VPN Interface there was standard DNS query and response. So it does
contacts internal DNS servers.

On ethernet card interface there was nothing.

BUT, nslookup says: Server:<ISP's server>, and then gives resolved IP. Why
does nslookup says that? Is it a bug in nslookup? To Microsoft: Please try
that and confirm is this a bug.

I am having a similar issue. My clients are using a Cisco VPN solution and
random clients will register their "A" records as their local LAN IP and not
the VPN Ip address?

"rem" wrote:

> Today I tried to detect the packet flow.
> I used two ethereals at the same time: one for VPN interface and one for
> ethernet card interface(ISP via cable). Then I tried nslookup.
>
> On VPN Interface there was standard DNS query and response. So it does
> contacts internal DNS servers.
>
> On ethernet card interface there was nothing.
>
> BUT, nslookup says: Server:<ISP's server>, and then gives resolved IP. Why
> does nslookup says that? Is it a bug in nslookup? To Microsoft: Please try
> that and confirm is this a bug.
>
>
>