I am using a Cisco VPN Concentrator and a Windows XP workstation. I have
created a "wide open" profile on the concentrator to allow me to log onto my domain over
the tunnel and access all my resources locally. The profile is wide open, and split
tunnelling is not enabled, so all traffic is routed over the tunnel while established.
This works very well.
However, the VPN Client PC gets an Ip from the ISP. When I log onto the machine and it
registers on my domain, the VPN Client assigns an address. In my DNS at the main campus,
the workstation gets registered in DNS with both IP's. The ISP is not valid (the
192.168.254.1) because I do not route that addess, nor do I want too.
See below....
U:\>ipconfig
> Windows IP Configuration
>
> Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . : domain.invalid
> IP Address. . . . . . . . . . . . : 192.168.254.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter Local Area Connection 3:
> Connection-specific DNS Suffix . : bcne-master1.bcne
> IP Address. . . . . . . . . . . . : 192.168.52.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.52.1
>
> U:\>nslookup testremote
> Server: jupiter.bcne-master1.bcne
> Address: 10.201.8.20
>
> Name: testremote.bcne-master1.bcne
> Addresses: 192.168.254.1, 192.168.52.16
>
So only the 192.168.52.16 is valid, the other isn't routed. How do I prevent this
behavior, either on the concentrator, on the client, or on the domain. I do not want both
addresses registered.
Thanks
