Just basic nslookp, from the client, results in my ISPs DNS server, but then I'd expect that as we're not using the VPN as the default gateway.
"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:OX8s%(E-Mail Removed)...
It should. It's the result of nslookup?
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
"Ben" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hi Bob,
I was thinking today, even if CMAK is causing the problem, it still gets it's IP from the DHCP server, and DHCP is set to register all connections with DNS, whether the client requests it or not. So shouldn't DHCP still be registering the VPN client connection in DNS, even if CMAK isn't registering the connection?
Ben
"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
Hi Ben,
Thank you for the update. We need that.
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
"Ben" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
Hi Robert,
I've just found out something interesting, I created a new VPN connection, just using the standard windows wizard, and not CMAK, took all the defaults, then set VPN to L2TP & smart cards, and changed the DNS tab in TCP/IP properties to append parent suffixes of the primary DNS suffix, added ourdomain.com as the DNS suffix, then checked both register this connection's address in DNS & Use this connection's DNS suffix.
When I made the VPN connection, and checked DNS, I found it was registering & updating perfectly.
So it must be something in the CMAK profile, but what I don't know!?
Ben
"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:%23E$(E-Mail Removed)...
Could the VPN client still use the local computer DNS? posting the results of nslookup and ping -a IP (here the IP is remote DNS IP).
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
"Ben" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hi,
I think we have some problems with our DHCP/DNS setup. We are using ISA 2004
for VPN & Firewall access, when our users connect via the VPN, their laptops
(WinXP sp2) aren't registering with DNS, although when they are in the
office on the LAN they do. ISA is configured to use our internal DHCP server
to issue out IPs, rather than issuing them from it's own static pool, and in
the advanced setup it's configured for DNS & wins to be issued via DHCP
also.
If you look at DHCP address leases it has 10 IPs leased to the ISA server
(unique ID - RAS), so ISA seems to be using the DHCP server correctly.
However if you look at the forward and reverse lookup zones in DNS none of
the IP details are registered.
Both DNS & DHCP are installed on the same server, windows 2003 sp1,
configured as a DC, DNS is AD integrated. ISA server is win2003 sp1,
standalone, using RADIUS to authenticate users with the DC.
DNS tab in the DHCP scope has:
Enable DNS dynamic updates - checked.
Always dynamically update DNS A & PTR records - selected.
Discard A & PTR records when lease is deleted - checked.
Dynamically update DNS A & PRT records for DHCP clients that do not request
updates.
DHCP lease is 5 days, DNS scavenging is 5 days, dynamic updates are secure
only.
I can't think of anything that might be wrong! Am I missing something? I
think it's starting to affect some of our applications, such as VoIP, as
name resolution isn't working.
Ben