VPN using local DNS instead of remote DNS

Hi,

I am having problem resolving to my office server while connecting from
remote via VPN.

1. After I connect via VPN, I could not resolve to the internal IP ( using
FQDN ), instead, nslookup uses my local dns server and return the public IP
instead.

2. When I use VISTA to connect via VPN, I have no problem. ie. it resolves
to the internal IP.

3. MY VPN server (W2003 server ) is also the DNS server and DC.

4. Internal domain name is the same as the public domain name.

Any help appreciated.

thanks

You may have many options. One of them are setup DNS suffix for VPN. This link may help.

Setup DNS Suffix for VPNA: Win2k and XP both use DNS to find other machines whereas Win98 uses NetBIOS or Wins. So, you will need to set up the DNS on VPN Server or clients. ...
http://www.howtonetworking.com/vpnis...ndnssuffix.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Jin" <(E-Mail Removed)> wrote in message news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)...
Hi,

I am having problem resolving to my office server while connecting from
remote via VPN.

1. After I connect via VPN, I could not resolve to the internal IP ( using
FQDN ), instead, nslookup uses my local dns server and return the public IP
instead.

2. When I use VISTA to connect via VPN, I have no problem. ie. it resolves
to the internal IP.

3. MY VPN server (W2003 server ) is also the DNS server and DC.

4. Internal domain name is the same as the public domain name.

Any help appreciated.

thanks

Hi,

Thanks for the help.

I feel that my issue may not be relating to DNS suffix, as I could not even
resolve the FQDN to the internal server. I tried anyway and it didn't work.

After connecting via VPN, i did a nslookup and the reply is actually from
the local DNS server instead of the DNS server at the remote site.

Like I mentioned, my Vista worked perfectly...strange...

tks

"Robert L [MVP - Networking]" wrote:

> You may have many options. One of them are setup DNS suffix for VPN. This link may help.
>
> Setup DNS Suffix for VPNA: Win2k and XP both use DNS to find other machines whereas Win98 uses NetBIOS or Wins. So, you will need to set up the DNS on VPN Server or clients. ...
> http://www.howtonetworking.com/vpnis...ndnssuffix.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Jin" <(E-Mail Removed)> wrote in message news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)...
> Hi,
>
> I am having problem resolving to my office server while connecting from
> remote via VPN.
>
> 1. After I connect via VPN, I could not resolve to the internal IP ( using
> FQDN ), instead, nslookup uses my local dns server and return the public IP
> instead.
>
> 2. When I use VISTA to connect via VPN, I have no problem. ie. it resolves
> to the internal IP.
>
> 3. MY VPN server (W2003 server ) is also the DNS server and DC.
>
> 4. Internal domain name is the same as the public domain name.
>
> Any help appreciated.
>
> thanks
>

Posting the results of ipconfig /all on both vista and xp here may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Jin" <(E-Mail Removed)> wrote in message news:3C3F7760-0271-426C-AADE-(E-Mail Removed)...
Hi,

Thanks for the help.

I feel that my issue may not be relating to DNS suffix, as I could not even
resolve the FQDN to the internal server. I tried anyway and it didn't work.

After connecting via VPN, i did a nslookup and the reply is actually from
the local DNS server instead of the DNS server at the remote site.

Like I mentioned, my Vista worked perfectly...strange...

tks

"Robert L [MVP - Networking]" wrote:

> You may have many options. One of them are setup DNS suffix for VPN. This link may help.
>
> Setup DNS Suffix for VPNA: Win2k and XP both use DNS to find other machines whereas Win98 uses NetBIOS or Wins. So, you will need to set up the DNS on VPN Server or clients. ...
> http://www.howtonetworking.com/vpnis...ndnssuffix.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Jin" <(E-Mail Removed)> wrote in message news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)...
> Hi,
>
> I am having problem resolving to my office server while connecting from
> remote via VPN.
>
> 1. After I connect via VPN, I could not resolve to the internal IP ( using
> FQDN ), instead, nslookup uses my local dns server and return the public IP
> instead.
>
> 2. When I use VISTA to connect via VPN, I have no problem. ie. it resolves
> to the internal IP.
>
> 3. MY VPN server (W2003 server ) is also the DNS server and DC.
>
> 4. Internal domain name is the same as the public domain name.
>
> Any help appreciated.
>
> thanks
>

Hi,

for Vista

Windows IP Configuration

Host Name . . . . . . . . . . . . : Action
Primary Dns Suffix . . . . . . . : itconsult.sg
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : itconsult.sg

PPP adapter Eastwest SG:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Ew SG
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.1.1.53(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 192.168.42.5
210.193.2.34
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area
Network)
Physical Address. . . . . . . . . : 00-16-CF-F1-98-B2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-A9-F2-43-93-A9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fea0::28aa:24a0:bfcf:546%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.7.121(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, 14 June, 2007 10:31:17 AM
Lease Expires . . . . . . . . . . : Thursday, 14 June, 2007 12:01:18 PM
Default Gateway . . . . . . . . . : 192.168.7.1
DHCP Server . . . . . . . . . . . : 192.168.7.1
DHCPv6 IAID . . . . . . . . . . . : 167778770
DNS Servers . . . . . . . . . . . : 192.168.7.8
192.168.7.6
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
Physical Address. . . . . . . . . : 00-A6-D3-37-E6-FF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-EA-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4136:e3a8:2cbb:2e02:3f57:f886(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::2cbb:2b02:3fc7:f886%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{F82A7F7C-9E69-4113-873D-49024DCAA
8E4}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 18:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{4AE184A0-D935-4FC7-B5F5-035F29E36
486}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.7.121%24(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.7.8
192.168.7.6
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 20:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{83B45B9D-247C-4C8C-8923-EFECABC2C
CA1}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
----------------------------------------------------------------

for XP

Windows IP Configuration

Host Name . . . . . . . . . . . . : Action2
Primary Dns Suffix . . . . . . . : itconsult.sg
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : itconsult.sg

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile
Connecti
on
Physical Address. . . . . . . . . : 00-11-25-AE-EE-63
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.7.125
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.7.1
DHCP Server . . . . . . . . . . . : 192.168.7.1
DNS Servers . . . . . . . . . . . : 192.168.7.8
192.168.7.6
Lease Obtained. . . . . . . . . . : Thursday, June 14, 2007 10:58:19
AM
Lease Expires . . . . . . . . . . : Thursday, June 14, 2007 11:58:19
AM

PPP adapter EW Sg:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-FF-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.1.54
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.1.1.54
DNS Servers . . . . . . . . . . . : 192.168.42.5
210.193.2.34

-----------------------------------------------------------------

Thanks for helping..

regards

"Robert L [MVP - Networking]" wrote:

> Posting the results of ipconfig /all on both vista and xp here may help.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Jin" <(E-Mail Removed)> wrote in message news:3C3F7760-0271-426C-AADE-(E-Mail Removed)...
> Hi,
>
> Thanks for the help.
>
> I feel that my issue may not be relating to DNS suffix, as I could not even
> resolve the FQDN to the internal server. I tried anyway and it didn't work.

>
> After connecting via VPN, i did a nslookup and the reply is actually from
> the local DNS server instead of the DNS server at the remote site.
>
> Like I mentioned, my Vista worked perfectly...strange...
>
> tks
>
> "Robert L [MVP - Networking]" wrote:
>
> > You may have many options. One of them are setup DNS suffix for VPN. This link may help.
> >
> > Setup DNS Suffix for VPNA: Win2k and XP both use DNS to find other machines whereas Win98 uses NetBIOS or Wins. So, you will need to set up the DNS on VPN Server or clients. ...
> > http://www.howtonetworking.com/vpnis...ndnssuffix.htm
> >
> >
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> > "Jin" <(E-Mail Removed)> wrote in message news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)...
> > Hi,
> >
> > I am having problem resolving to my office server while connecting from
> > remote via VPN.
> >
> > 1. After I connect via VPN, I could not resolve to the internal IP ( using
> > FQDN ), instead, nslookup uses my local dns server and return the public IP
> > instead.
> >
> > 2. When I use VISTA to connect via VPN, I have no problem. ie. it resolves
> > to the internal IP.
> >
> > 3. MY VPN server (W2003 server ) is also the DNS server and DC.
> >
> > 4. Internal domain name is the same as the public domain name.
> >
> > Any help appreciated.
> >
> > thanks
> >

I saw several threads here on eggheadcafe.com about VPN DNS failures, and none of the threads had answers on them.

I was able to resolve the VPN DNS issue with the instructions in this article:

Article ID: 311218 - Last Review: February 28, 2007 - Revision: 3.5
Cannot Change the Binding Order for Remote Access Connections
http://support.microsoft.com/kb/311218

Good luck!

> On Monday, June 11, 2007 9:04 AM Ji wrote:

> Hi,
>
> I am having problem resolving to my office server while connecting from
> remote via VPN.
>
> 1. After I connect via VPN, I could not resolve to the internal IP ( using
> FQDN ), instead, nslookup uses my local dns server and return the public IP
> instead.
>
> 2. When I use VISTA to connect via VPN, I have no problem. ie. it resolves
> to the internal IP.
>
> 3. MY VPN server (W2003 server ) is also the DNS server and DC.
>
> 4. Internal domain name is the same as the public domain name.
>
> Any help appreciated.
>
> thanks

>> On Monday, June 11, 2007 10:27 PM Robert L [MVP - Networking] wrote:

>> This is a multi-part message in MIME format.
>>
>> ------=_NextPart_000_0019_01C7ACDC.481692D0
>> Content-Type: text/plain;
>> charset="Utf-8"
>> Content-Transfer-Encoding: quoted-printable
>>
>> You may have many options. One of them are setup DNS suffix for VPN. =
>> This link may help.
>>
>> Setup DNS Suffix for VPNA: Win2k and XP both use DNS to find other =
>> machines whereas Win98 uses NetBIOS or Wins. So, you will need to set up =
>> the DNS on VPN Server or clients. ...
>> http://www.howtonetworking.com/vpnis...ndnssuffix.htm =20
>>
>>
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on =
>> http://www.ChicagoTech.net=20
>> How to Setup Windows, Network, VPN & Remote Access on =
>> http://www.HowToNetworking.com=20
>> "Jin" <(E-Mail Removed)> wrote in message =
>> news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)...
>> Hi,
>>
>> I am having problem resolving to my office server while connecting =
>> from=20
>> remote via VPN.
>>
>> 1. After I connect via VPN, I could not resolve to the internal IP ( =
>> using=20
>> FQDN ), instead, nslookup uses my local dns server and return the =
>> public IP=20
>> instead.
>>
>> 2. When I use VISTA to connect via VPN, I have no problem. ie. it =
>> resolves=20
>> to the internal IP.
>>
>> 3. MY VPN server (W2003 server ) is also the DNS server and DC.
>>
>> 4. Internal domain name is the same as the public domain name.
>>
>> Any help appreciated.
>>
>> thanks
>>
>> ------=_NextPart_000_0019_01C7ACDC.481692D0
>> Content-Type: text/html;
>> charset="Utf-8"
>> Content-Transfer-Encoding: quoted-printable
>>
>> =EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>> <HTML><HEAD>
>> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
>> <META content=3D"MSHTML 6.00.6000.16441" name=3DGENERATOR>
>> <STYLE></STYLE>
>> </HEAD>
>> <BODY bgColor=3D#ffffff>
>> <DIV>You may have many options. One of them are setup DNS suffix for =
>> VPN. This=20
>> link may help.</DIV>
>> <DIV> </DIV>
>> <DIV><A class=3Dl onmousedown=3D"return clk(0,'','','cres','1','')"=20
>> href=3D"http://www.howtonetworking.com/vpnissues/vpndnssuffix.htm"><FONT =
>>
>> color=3D#663399>Setup <B>DNS</B> Suffix for <B>VPN</B></FONT></A>
>> <TABLE cellSpacing=3D0 cellPadding=3D0 border=3D0>
>> <TBODY>
>> <TR>
>> <TD class=3Dj><FONT size=3D-1>A: Win2k and XP both use <B>DNS</B> to =
>> find=20
>> other machines whereas Win98 uses NetBIOS or Wins. So, you will =
>> need to=20
>> set up the <B>DNS</B> on <B>VPN</B> Server or clients. =
>> <B>...</B><BR><SPAN=20
>> class=3Da><FONT color=3D#008000><A=20
>> =
>> href=3D"http://www.howtonetworking.com/vpnissues/vpndnssuffix.htm">http:/=
>> /www.howtonetworking.com/<B>vpn</B>issues/<B>vpn</B><B>dns</B>suffix.htm<=
>> /A>=20
>> </FONT></SPAN></FONT></TD></TR></TBODY></TABLE></DIV>
>> <DIV><BR>Bob Lin, MS-MVP, MCSE & CNE<BR>Networking, Internet, =
>> Routing, VPN=20
>> Troubleshooting on <A=20
>> href=3D"http://www.ChicagoTech.net">http://www.ChicagoTech.net</A> =
>> <BR>How to=20
>> Setup Windows, Network, VPN & Remote Access on <A=20
>> href=3D"http://www.HowToNetworking.com">http://www.HowToNetworking.com</A=
>> <BLOCKQUOTE=20
>> style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>> BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
>> <DIV>"Jin" <<A=20
>> =
>> href=3D"private.php?do=newpm&u=">Jin@ discussions.microsoft.c=
>> om</A>>=20
>> wrote in message <A=20
>> =
>> href=3D"news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)">news:C40=
>> A19C2-2ADC-40B0-B07E-(E-Mail Removed)</A>...</DIV>Hi,<BR><BR>I =
>>
>> am having problem resolving to my office server while connecting from=20
>> <BR>remote via VPN.<BR><BR>1. After I connect via VPN, I could not =
>> resolve to=20
>> the internal IP ( using <BR>FQDN ), instead, nslookup uses my local =
>> dns server=20
>> and return the public IP <BR>instead.<BR><BR>2. When I use VISTA to =
>> connect=20
>> via VPN, I have no problem. ie. it resolves <BR>to the internal =
>> IP.<BR><BR>3.=20
>> MY VPN server (W2003 server ) is also the DNS server and DC.<BR><BR>4. =
>>
>> Internal domain name is the same as the public domain name.<BR><BR>Any =
>> help=20
>> appreciated.<BR><BR>thanks<BR></BLOCKQUOTE></BODY></HTML>
>>
>> ------=_NextPart_000_0019_01C7ACDC.481692D0--

>>> On Tuesday, June 12, 2007 3:29 AM Ji wrote:

>>> Hi,
>>>
>>> Thanks for the help.
>>>
>>> I feel that my issue may not be relating to DNS suffix, as I could not even
>>> resolve the FQDN to the internal server. I tried anyway and it didn't work.

>>>
>>> After connecting via VPN, i did a nslookup and the reply is actually from
>>> the local DNS server instead of the DNS server at the remote site.
>>>
>>> Like I mentioned, my Vista worked perfectly...strange...
>>>
>>> tks
>>>
>>> "Robert L [MVP - Networking]" wrote:

>>>> On Wednesday, June 13, 2007 9:34 PM Robert L [MVP - Networking] wrote:

>>>> This is a multi-part message in MIME format.
>>>>
>>>> ------=_NextPart_000_0013_01C7AE67.2B41DE30
>>>> Content-Type: text/plain;
>>>> charset="Utf-8"
>>>> Content-Transfer-Encoding: quoted-printable
>>>>
>>>> Posting the results of ipconfig /all on both vista and xp here may help.
>>>>
>>>> Bob Lin, MS-MVP, MCSE & CNE
>>>> Networking, Internet, Routing, VPN Troubleshooting on =
>>>> http://www.ChicagoTech.net=20
>>>> How to Setup Windows, Network, VPN & Remote Access on =
>>>> http://www.HowToNetworking.com=20
>>>> "Jin" <(E-Mail Removed)> wrote in message =
>>>> news:3C3F7760-0271-426C-AADE-(E-Mail Removed)...
>>>> Hi,
>>>>
>>>> Thanks for the help.
>>>>
>>>> I feel that my issue may not be relating to DNS suffix, as I could not =
>>>> even=20
>>>> resolve the FQDN to the internal server. I tried anyway and it didn't =
>>>> work.

>>>>
>>>> After connecting via VPN, i did a nslookup and the reply is actually =
>>>> from=20
>>>> the local DNS server instead of the DNS server at the remote site.
>>>>
>>>> Like I mentioned, my Vista worked perfectly...strange...
>>>>
>>>> tks
>>>>
>>>> "Robert L [MVP - Networking]" wrote:
>>>>
>>>> > You may have many options. One of them are setup DNS suffix for VPN. =
>>>> This link may help.
>>>> >=20
>>>> > Setup DNS Suffix for VPNA: Win2k and XP both use DNS to find other =
>>>> machines whereas Win98 uses NetBIOS or Wins. So, you will need to set up =
>>>> the DNS on VPN Server or clients. ...
>>>> > http://www.howtonetworking.com/vpnis...ndnssuffix.htm =20
>>>> >=20
>>>> >=20
>>>> > Bob Lin, MS-MVP, MCSE & CNE
>>>> > Networking, Internet, Routing, VPN Troubleshooting on =
>>>> http://www.ChicagoTech.net=20
>>>> > How to Setup Windows, Network, VPN & Remote Access on =
>>>> http://www.HowToNetworking.com=20
>>>> > "Jin" <(E-Mail Removed)> wrote in message =
>>>> news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)...
>>>> > Hi,
>>>> >=20
>>>> > I am having problem resolving to my office server while connecting =
>>>> from=20
>>>> > remote via VPN.
>>>> >=20
>>>> > 1. After I connect via VPN, I could not resolve to the internal IP =
>>>> ( using=20
>>>> > FQDN ), instead, nslookup uses my local dns server and return the =
>>>> public IP=20
>>>> > instead.
>>>> >=20
>>>> > 2. When I use VISTA to connect via VPN, I have no problem. ie. it =
>>>> resolves=20
>>>> > to the internal IP.
>>>> >=20
>>>> > 3. MY VPN server (W2003 server ) is also the DNS server and DC.
>>>> >=20
>>>> > 4. Internal domain name is the same as the public domain name.
>>>> >=20
>>>> > Any help appreciated.
>>>> >=20
>>>> > thanks
>>>> >
>>>> ------=_NextPart_000_0013_01C7AE67.2B41DE30
>>>> Content-Type: text/html;
>>>> charset="Utf-8"
>>>> Content-Transfer-Encoding: quoted-printable
>>>>
>>>> =EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>>>> <HTML><HEAD>
>>>> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
>>>> <META content=3D"MSHTML 6.00.6000.16441" name=3DGENERATOR>
>>>> <STYLE></STYLE>
>>>> </HEAD>
>>>> <BODY bgColor=3D#ffffff>
>>>> <DIV>Posting the results of ipconfig /all on both vista and xp here may=20
>>>> help.</DIV>
>>>> <DIV><BR>Bob Lin, MS-MVP, MCSE & CNE<BR>Networking, Internet, =
>>>> Routing, VPN=20
>>>> Troubleshooting on <A=20
>>>> href=3D"http://www.ChicagoTech.net">http://www.ChicagoTech.net</A> =
>>>> <BR>How to=20
>>>> Setup Windows, Network, VPN & Remote Access on <A=20
>>>> href=3D"http://www.HowToNetworking.com">http://www.HowToNetworking.com</A=
>>>> <BLOCKQUOTE=20
>>>> style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>>>> BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
>>>> <DIV>"Jin" <<A=20
>>>> =
>>>> href=3D"private.php?do=newpm&u=">Jin@ discussions.microsoft.c=
>>>> om</A>>=20
>>>> wrote in message <A=20
>>>> =
>>>> href=3D"news:3C3F7760-0271-426C-AADE-(E-Mail Removed)">news:3C3=
>>>> F7760-0271-426C-AADE-(E-Mail Removed)</A>...</DIV>Hi,<BR><BR>Th=
>>>> anks=20
>>>> for the help.<BR><BR>I feel that my issue may not be relating to DNS =
>>>> suffix,=20
>>>> as I could not even <BR>resolve the FQDN to the internal server. I =
>>>> tried=20
>>>> anyway and it didn't work.

<BR><BR>After connecting via VPN, i did a =
>>>>
>>>> nslookup and the reply is actually from <BR>the local DNS server =
>>>> instead of=20
>>>> the DNS server at the remote site.<BR><BR>Like I mentioned, my Vista =
>>>> worked=20
>>>> perfectly...strange...<BR><BR>tks<BR><BR>"Robert L [MVP - Networking]" =
>>>>
>>>> wrote:<BR><BR>> You may have many options. One of them are setup =
>>>> DNS suffix=20
>>>> for VPN. This link may help.<BR>> <BR>> Setup DNS Suffix for =
>>>> VPNA: Win2k=20
>>>> and XP both use DNS to find other machines whereas Win98 uses NetBIOS =
>>>> or Wins.=20
>>>> So, you will need to set up the DNS on VPN Server or clients.=20
>>>> ...<BR>>       <A=20
>>>> =
>>>> href=3D"http://www.howtonetworking.com/vpnissues/vpndnssuffix.htm">http:/=
>>>> /www.howtonetworking.com/vpnissues/vpndnssuffix.htm</A> =20
>>>> <BR>> <BR>> <BR>> Bob Lin, MS-MVP, MCSE & CNE<BR>> =
>>>> Networking,=20
>>>> Internet, Routing, VPN Troubleshooting on <A=20
>>>> href=3D"http://www.ChicagoTech.net">http://www.ChicagoTech.net</A> =
>>>> <BR>> How=20
>>>> to Setup Windows, Network, VPN & Remote Access on <A=20
>>>> =
>>>> href=3D"http://www.HowToNetworking.com">http://www.HowToNetworking.com</A=
>>>> <BR>>   "Jin" <<A=20
>>>> =
>>>> href=3D"private.php?do=newpm&u=">Jin@ discussions.microsoft.c=
>>>> om</A>>=20
>>>> wrote in message <A=20
>>>> =
>>>> href=3D"news:C40A19C2-2ADC-40B0-B07E-(E-Mail Removed)">news:C40=
>>>> A19C2-2ADC-40B0-B07E-(E-Mail Removed)</A>...<BR>> &nbsp=
>>>> ;=20
>>>> Hi,<BR>> <BR>>   I am having problem resolving to my =
>>>> office=20
>>>> server while connecting from <BR>>   remote via =
>>>> VPN.<BR>>=20
>>>> <BR>>   1. After I connect via VPN, I could not resolve =
>>>> to the=20
>>>> internal IP ( using <BR>>   FQDN ), instead, nslookup =
>>>> uses my=20
>>>> local dns server and return the public IP <BR>>  =20
>>>> instead.<BR>> <BR>>   2. When I use VISTA to connect =
>>>> via VPN,=20
>>>> I have no problem. ie. it resolves <BR>>   to the =
>>>> internal=20
>>>> IP.<BR>> <BR>>   3. MY VPN server (W2003 server ) is =
>>>> also the=20
>>>> DNS server and DC.<BR>> <BR>>   4. Internal domain =
>>>> name is the=20
>>>> same as the public domain name.<BR>> <BR>>   Any help=20
>>>> appreciated.<BR>> <BR>>  =20
>>>> thanks<BR>></BLOCKQUOTE></BODY></HTML>
>>>>
>>>> ------=_NextPart_000_0013_01C7AE67.2B41DE30--

>>>>> On Wednesday, June 13, 2007 11:17 PM Ji wrote:

>>>>> Hi,
>>>>>
>>>>> for Vista
>>>>>
>>>>>
>>>>> Windows IP Configuration
>>>>>
>>>>> Host Name . . . . . . . . . . . . : Action
>>>>> Primary Dns Suffix . . . . . . . : itconsult.sg
>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>> IP Routing Enabled. . . . . . . . : No
>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>> DNS Suffix Search List. . . . . . : itconsult.sg
>>>>>
>>>>> PPP adapter Eastwest SG:
>>>>>
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : Ew SG
>>>>> Physical Address. . . . . . . . . :
>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>> IPv4 Address. . . . . . . . . . . : 10.1.1.53(Preferred)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>>>>> Default Gateway . . . . . . . . . : 0.0.0.0
>>>>> DNS Servers . . . . . . . . . . . : 192.168.42.5
>>>>> 210.193.2.34
>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>>>
>>>>> Ethernet adapter Bluetooth Network Connection:
>>>>>
>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : Bluetooth Device (Personal Area
>>>>> Network)
>>>>> Physical Address. . . . . . . . . : 00-16-CF-F1-98-B2
>>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>
>>>>> Wireless LAN adapter Wireless Network Connection:
>>>>>
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
>>>>> Con
>>>>> nection
>>>>> Physical Address. . . . . . . . . : 00-A9-F2-43-93-A9
>>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>> Link-local IPv6 Address . . . . . : fea0::28aa:24a0:bfcf:546%10(Preferred)
>>>>> IPv4 Address. . . . . . . . . . . : 192.168.7.121(Preferred)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Lease Obtained. . . . . . . . . . : Thursday, 14 June, 2007 10:31:17 AM
>>>>> Lease Expires . . . . . . . . . . : Thursday, 14 June, 2007 12:01:18 PM
>>>>> Default Gateway . . . . . . . . . : 192.168.7.1
>>>>> DHCP Server . . . . . . . . . . . : 192.168.7.1
>>>>> DHCPv6 IAID . . . . . . . . . . . : 167778770
>>>>> DNS Servers . . . . . . . . . . . : 192.168.7.8
>>>>> 192.168.7.6
>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>>>
>>>>> Ethernet adapter Local Area Connection:
>>>>>
>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
>>>>> Physical Address. . . . . . . . . : 00-A6-D3-37-E6-FF
>>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>
>>>>> Tunnel adapter Local Area Connection* 6:
>>>>>
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
>>>>> Physical Address. . . . . . . . . : 02-00-EA-55-4E-01
>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>> IPv6 Address. . . . . . . . . . . :
>>>>> 2001:0:4136:e3a8:2cbb:2e02:3f57:f886(Pref
>>>>> erred)
>>>>> Link-local IPv6 Address . . . . . : fe80::2cbb:2b02:3fc7:f886%11(Preferred)
>>>>> Default Gateway . . . . . . . . . : ::
>>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
>>>>>
>>>>> Tunnel adapter Local Area Connection* 7:
>>>>>
>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . :
>>>>> isatap.{F82A7F7C-9E69-4113-873D-49024DCAA
>>>>> 8E4}
>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>
>>>>> Tunnel adapter Local Area Connection* 18:
>>>>>
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . :
>>>>> isatap.{4AE184A0-D935-4FC7-B5F5-035F29E36
>>>>> 486}
>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>> Link-local IPv6 Address . . . . . : fe80::5efe:192.168.7.121%24(Preferred)
>>>>> Default Gateway . . . . . . . . . :
>>>>> DNS Servers . . . . . . . . . . . : 192.168.7.8
>>>>> 192.168.7.6
>>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
>>>>>
>>>>> Tunnel adapter Local Area Connection* 20:
>>>>>
>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . :
>>>>> isatap.{83B45B9D-247C-4C8C-8923-EFECABC2C
>>>>> CA1}
>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>> ----------------------------------------------------------------
>>>>>
>>>>> for XP
>>>>>
>>>>> Windows IP Configuration
>>>>>
>>>>> Host Name . . . . . . . . . . . . : Action2
>>>>> Primary Dns Suffix . . . . . . . : itconsult.sg
>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>> IP Routing Enabled. . . . . . . . : No
>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>> DNS Suffix Search List. . . . . . : itconsult.sg
>>>>>
>>>>> Ethernet adapter Local Area Connection:
>>>>>
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile
>>>>> Connecti
>>>>> on
>>>>> Physical Address. . . . . . . . . : 00-11-25-AE-EE-63
>>>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>> IP Address. . . . . . . . . . . . : 192.168.7.125
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.7.1
>>>>> DHCP Server . . . . . . . . . . . : 192.168.7.1
>>>>> DNS Servers . . . . . . . . . . . : 192.168.7.8
>>>>> 192.168.7.6
>>>>> Lease Obtained. . . . . . . . . . : Thursday, June 14, 2007 10:58:19
>>>>> AM
>>>>> Lease Expires . . . . . . . . . . : Thursday, June 14, 2007 11:58:19
>>>>> AM
>>>>>
>>>>> PPP adapter EW Sg:
>>>>>
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>>>>> Physical Address. . . . . . . . . : 00-53-45-00-FF-00
>>>>> Dhcp Enabled. . . . . . . . . . . : No
>>>>> IP Address. . . . . . . . . . . . : 10.1.1.54
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>>>>> Default Gateway . . . . . . . . . : 10.1.1.54
>>>>> DNS Servers . . . . . . . . . . . : 192.168.42.5
>>>>> 210.193.2.34
>>>>>
>>>>>
>>>>> -----------------------------------------------------------------
>>>>>
>>>>> Thanks for helping..
>>>>>
>>>>> regards
>>>>>
>>>>>
>>>>>
>>>>> "Robert L [MVP - Networking]" wrote:

>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>> Composite UI Pattern and RAD Development for Data Entry Applications, Part 1
>>>>> http://www.eggheadcafe.com/tutorials...ns-part-1.aspx

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Add remote local account to local file security	Rick E	Windows XP Security	1	19th June 2007 03:13 PM
Is there anyway to prevent a local logon to a remote desktop from terminating the remote session?		Windows XP Remote Working	2	2nd August 2004 07:13 AM
local&remote	Jennie	Windows XP Remote Working	1	11th May 2004 06:14 PM
Windows XP PRO Remote Desktop Printing to a local printer from a remote session	Richard Moreno	Windows XP Remote Working	10	4th May 2004 02:46 PM
Redirecting Local Serial Port to Remote Computer using Remote Desktop	Tyler Pannier	Windows XP Remote Working	0	24th October 2003 02:21 PM