Vista and SecureClient VPN DNS issues.

Hi guys,

I'm having fun with a vista laptop and configuring it to connection to
our Checkpoint SecureCient VPN over dial-up.

The machine will connect to the VPN but it is using the ISP (dial-up
connection) dns server rather than our internal servers as pushed out
by the VPN client. When I run ipconfig /all I can see that the VPN
connection has got the DNS servers configured, but when I run nslookup
it is defaulting to the external DNS server.

Windows XP/2000 clients do not experience this problem, in fact they
never have.

Is there any way that I can change the Vista Primary DNS server for
all connections? Can this be automated by the SecureClient.. or am I
simply missing a trick?

Thanks in advance....

.

Relevant Pages

  • VPN fails over dial-up after 4 minutes
    ... began testing VPN access to our network over dial-up for our laptop users. ... Initiate a dial-up connection to the internet. ... Initiate the VPN connection using the shortcut called "Connect to Small ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN fails over dial-up after 4 minutes
    ... > install of XP Pro on it, alongside his existing 2k Pro installation. ... > VPN connection to the SBS over both broadband and dial-up connections. ...
    (microsoft.public.windows.server.sbs)
  • Re: Switch DNS servers on the fly
    ... How can I change my primary DNS server with a batch file or something so instead of pointing to my home ISPs DNS server first it will point to the DNS server of my VPN connection? ... By default, any VPN client you use, once connected, will use the VPN's IP configuration, which should be the internal DNS of the network you're connecting to because by default, the VPN interface on the client will be on top of the binding order. ...
    (microsoft.public.windows.server.dns)
  • Re: Strange DNS
    ... >> You are trying to lookup a resource located in your office. ... the ISP DNS server is not able to locate the record. ... >> inside your office are now tunnelled through the VPN connection. ...
    (microsoft.public.win2000.dns)
  • Re: Strange DNS
    ... the ISP DNS server is not able to locate the record. ... >>> inside your office are now tunnelled through the VPN connection. ... and why couldnt the internal DNS server solve this adress when conencted ...
    (microsoft.public.win2000.dns)