Register connection address in DNS for VPN clients is only temporary and not sustainable??

[Joe Mine]

Hi, I've a VPN client and I can appended the DNS suffixes and register the
connection address in DNS temporarily for the initial period, but it is not
sustainable and disappear after a while when the VPN connection is still
maintained. Meaning the VPN client ip address/netbios name is registered in
DNS temporarily for only the initial period of maybe two hours then
dissappear. Why can't it be permanent for as long as the VPN client is logon
into the network through VPN? How do I make the VPN client DNS registration
permanent???
The current DNS settings in Advanced TCP/IP settings of the VPN client are
as follows:
Append these DNS suffixes(in order): mydomain.local
DNS suffix for this connection: mydomain.local
[Tick] Register this connection's addresses in DNS
[Tick] Use this connection's DNS suffix in DNS registration.

 

[Ace Fekay [MVP]]

In

Hi, I've a VPN client and I can appended the DNS suffixes and
register the connection address in DNS temporarily for the initial
period, but it is not sustainable and disappear after a while when
the VPN connection is still maintained. Meaning the VPN client ip
address/netbios name is registered in DNS temporarily for only the
initial period of maybe two hours then dissappear. Why can't it be
permanent for as long as the VPN client is logon into the network
through VPN? How do I make the VPN client DNS registration
permanent???
The current DNS settings in Advanced TCP/IP settings of the VPN
client are as follows:
Append these DNS suffixes(in order): mydomain.local
DNS suffix for this connection: mydomain.local
[Tick] Register this connection's addresses in DNS
[Tick] Use this connection's DNS suffix in DNS registration.

This is a usual problem with VPNs and AD. HOSTS files are the answer to this
ugly issue. So try using a hosts file with the DC's FQDN and it should work.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Joe M]

Ace,
Is it hosts file or lmhosts files? I already use an lmhosts file on
the VPN client. And the VPN client will be assign a dynamic ip address from
the VPN server, which changes everytime. How do I create a "hosts file with
the DC's FQDN " ? Please list the steps, thanks in advanced.



"Ace Fekay [MVP]"

In

Hi, I've a VPN client and I can appended the DNS suffixes and
register the connection address in DNS temporarily for the initial
period, but it is not sustainable and disappear after a while when
the VPN connection is still maintained. Meaning the VPN client ip
address/netbios name is registered in DNS temporarily for only the
initial period of maybe two hours then dissappear. Why can't it be
permanent for as long as the VPN client is logon into the network
through VPN? How do I make the VPN client DNS registration
permanent???
The current DNS settings in Advanced TCP/IP settings of the VPN
client are as follows:
Append these DNS suffixes(in order): mydomain.local
DNS suffix for this connection: mydomain.local
[Tick] Register this connection's addresses in DNS
[Tick] Use this connection's DNS suffix in DNS registration.

This is a usual problem with VPNs and AD. HOSTS files are the answer to this
ugly issue. So try using a hosts file with the DC's FQDN and it should work.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

In

Ace,
Is it hosts file or lmhosts files? I already use an lmhosts
file on the VPN client. And the VPN client will be assign a dynamic
ip address from the VPN server, which changes everytime. How do I
create a "hosts file with the DC's FQDN " ? Please list the steps,
thanks in advanced.

You would use a HOSTS file. LMHOSTS are for NetBIOS names and not needed in
your scenario. HOSTS files are for FQDNs and TCP/IP hostnames.

There's a default HOSTS file in your system32\etc\services folder. Modify
that in the client PC to include such things as your domian controllers so
it knows how to get to them for logon and authentication purposes. Add
something like this to the end of it and save it, then test it out:

192.168.5.200 dc1.domain.com
192.168.5.201 dc2.domain.com



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory