Cisco VPN Client and DNS

[mdabney]

We use the Cisco VPN client 4.6x for our remote users. Our remote users have a subnet of 192.168.33.x. Our internal domain is 10.10.3.x. They are both on the same domain. We had no problems with name resolution up until about a month ago when we lost a DNS server and had to replace it. Both subnets are in the subnet list, but nothing from 192.168.33.x can see the network. You can't ping by name, nor can you use any programs that connect using UNC. I can connect by using IP. No one internally on 10 network has any problems. I've check the PIX and the VPN is set to use the DNS server we have for resolution. What am I missing? I'd appreciate any help.

 

[GlenJohnson]

What are you using for a firewall? Maybe it's blocking the vpn. Just a quick thought. Good luck.

Glen A. Johnson
If you like fun and sun, check out Tek-Tips Florida Forum
"Maybe this world is another planet's hell."
Aldous Huxley (1894-1963), English critic & novelist

 

[mdabney]

I have a PIX 510 and I made sure the DNS was specified in the config.

 

[GlenJohnson]

Have you checked the logs on the server for a clue? Usually one of the first places I start. Just a thought.

Glen A. Johnson
If you like fun and sun, check out Tek-Tips Florida Forum
"Maybe this world is another planet's hell."
Aldous Huxley (1894-1963), English critic & novelist

 

[joepc]

So you can ping the DNS server and you are sure that no DNS ports are being blocked in anyway?

What are you using for a DNS server?\

Have you tried NSlookup at just to see if that works?

Can you ping the FQDN?

 

[mdabney]

There are not errors or warnings in the log. From the remote machines, I can't ping anything but by IP. From the PIX, however, I can ping by FQDN and just name. We are using Windows 2000 server for DNS. NSlookup from the remote machines also does not work. I can't find anything in the DNS that would give me a problem.