Re: VPN connection cannot resolve host name
- From: "Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 27 Nov 2005 13:00:35 -0800
OK, so now do an nslookup for a local address, an Internet address, and a
remote network address and see which server is being queried for each
lookup. A real common way to overcome this is to put the remote network DNS
server as the primary and your ISP's DNS as the secondary. Then when the VPN
is disconnected DNS will fall back to the second entry, and when connected
use the remote.
....kurt
"A. Barnett" <barnet@xxxxxxxxx> wrote in message
news:Q%oif.5035$q93.1494883@xxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thanks, Bob,
>
> Here are the two IPCONFIG/ALLs, from the XP and the W2K PCs. (I have
> dummied
> up the numbers - hope that doesn't mess things up to much.) Note that both
> listings are inside the VPN connection. XP Pro does fine, but W2K can only
> use IP addresses to navigate the inter/intranets.
>
> 1) XP Pro (this PC will resolve host names inside the VPN, either intranet
> or internet):
>
> IPCONFIG/ALL >ipconfig_xp.txt
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : <dummy_xp>
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : <dummya.dummyb>.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : <dummy1.dummy2>.com
> Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX
> NIC (3C905B-TX)
> Physical Address. . . . . . . . . : aa-bb-cc-dd-ee-ff
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.<dummy1.dummy2>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.<dummy1.dummy3>
> DHCP Server . . . . . . . . . . . : 192.168.<dummy1.dummy3>
> DNS Servers . . . . . . . . . . . : <A.B.C.D1>
> <A.B.C.D2>
> <A.B.C.D3>
> Lease Obtained. . . . . . . . . . : Saturday, November 26, 2005
> 7:29:19 AM
> Lease Expires . . . . . . . . . . : Tuesday, November 29, 2005
> 7:29:19 AM
>
> Ethernet adapter {44A0A5C7-F9CD-41F5-BD30-E09E0303959D}:
>
> Connection-specific DNS Suffix . : dummya.dummyb.local
> Description . . . . . . . . . . . : Nortel IPSECSHM Adapter -
> Packet
> Scheduler Miniport
> Physical Address. . . . . . . . . : aa-bb-cc-dd-ee-ff
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 172.<b.c.d>
> Subnet Mask . . . . . . . . . . . : 255.255.254.0
> Default Gateway . . . . . . . . . : 172.<b.c.d1>
> DNS Servers . . . . . . . . . . . : 172.<b.c.d2>
> 172.<b.c.d3>
> Primary WINS Server . . . . . . . : 172.<b.c.d4>
> Secondary WINS Server . . . . . . : 172.<b.c.d5>
>
>
> ==============================================================
>
> 2) W2K Pro (this PC will not resolve host names inside VPN connection -
> neither intranet nor internet):
>
> IPCONFIG/ALL >ipconfig_w2k.txt
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : <dummy>
> Primary DNS Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : <dummy1.dummy2.com>
>
> Ethernet adapter {A67D8438-3BD9-4BB1-AD62-9FFFA07151E7}:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : NOC Extranet Access Adapter
> Physical Address. . . . . . . . . : aa-bb-cc-dd-ee-ff
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Autoconfiguration IP Address. . . : 172.<b.c.d1>
> Subnet Mask . . . . . . . . . . . : 255.255.254.0
> Default Gateway . . . . . . . . . : 172.<b.c.d2>
> DNS Servers . . . . . . . . . . . :
>
> Ethernet adapter Local Area Connection 2:
>
> Connection-specific DNS Suffix . : <dummy1.dummy2.com>
> Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
> Ethernet NIC
> Physical Address. . . . . . . . . : aa-bb-cc-dd-ee-ff
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.<dummya.dummyb>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.<dummya.dummyb1>
> DHCP Server . . . . . . . . . . . : 192.168.<dummya.dummyb2>
> DNS Servers . . . . . . . . . . . : <dummy1.dummy2.dummy3.dummy4>
> <dummy1.dummy2.dummy3.dummy5>
> <dummy1.dummy2.dummy3.dummy6>
> Lease Obtained. . . . . . . . . . : Sunday, November 27, 2005 6:19:55 AM
> Lease Expires . . . . . . . . . . : Wednesday, November 30, 2005 6:19:55
> AM
>
> "Robert L [MS-MVP]" <noreply@xxxxxxxxxxx> wrote in message
> news:%23aYJrN38FHA.444@xxxxxxxxxxxxxxxxxxxxxxx
> posting the result of both computer ipconfig /all here may help.
>
>
.
- Follow-Ups:
- Re: VPN connection cannot resolve host name
- From: A. Barnett
- Re: VPN connection cannot resolve host name
- References:
- VPN connection cannot resolve host name
- From: A. Barnett
- Re: VPN connection cannot resolve host name
- From: Robert L [MS-MVP]
- Re: VPN connection cannot resolve host name
- From: A. Barnett
- VPN connection cannot resolve host name
- Prev by Date: Re: VPN connection cannot resolve host name
- Next by Date: Re: VPN connection cannot resolve host name
- Previous by thread: Re: VPN connection cannot resolve host name
- Next by thread: Re: VPN connection cannot resolve host name
- Index(es):
Relevant Pages
|