Issue: Cisco VPN Client

I have been experiencing an issue with a Cisco VPN Client while connecting to a government site.  The problem began occuring when we moved the workstation that it is on to a new domain.  Once on the new domain we could not contact the site (our connection would fail).  
If I move the workstation back to the old domain, the user can connect to the site via the VPN no problem.

I believe that it may be a DNS issue.  Our old domain was a NT 4.0 domain controller and the new one is an Active Directory domain.  Prior to the new domain our DHCP would point users to the ISP's external DNS, because of AD the new DHCP points to the internal DNS which is also the AD server.

Any ideas?

Please help!
MightyMikeyAsked:
Who is Participating?
 
chakkoCommented:
you can use the hosts file to bypass/workaround a DNS or name resolution problem.

try making an entry in your hosts file  (c:\windows\system32\drivers\etc\hosts )

add an entry for the IP and name:

xxx.xxx.xxx.xxx   prefix2.domain.com


add entries for other hosts if you need to.

if you need to connect by netbios name you can make the entry like this:

xxx.xxx.xxx.xxx   prefix2    prefix2.domain.com



0
 
RPPreacherCommented:
Is the vpn client pointing to a name or IP?
What are the ping results new domain versus old domain?
0
 
MightyMikeyAuthor Commented:
The vpn client points to a name (prefix.domain.com), although i've tried changing it to an IP, but i was still frustrated by failure.  The vpn client can connect to the vpn server on the new domain because it authenticated and showed a stable connection, but the actual application that uses and runs on the vpn cannot access its intended host through the vpn on the new domain.  Everything works fine on the old.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
RPPreacherCommented:
When you attempt to ping prefix.domain.com on the new domain, what are the results?
0
 
MightyMikeyAuthor Commented:
I can ping the VPN host from both domains, but i cannot ping the server/IP that the application communicates with once the vpn connection is up between the new domain and the vpn server.

Does that make sense?
0
 
RPPreacherCommented:
If I understand, you are saying that you CAN make a VPN connection from both domains; however, once connected, the client cannot ping the destination server by name?

If this is accurate, when you ping the name of the destination server, what is the result?
0
 
MightyMikeyAuthor Commented:
when i ping the final destination on the remote network prefix2.domain.com i receive a message saying:  "Ping request could not find host prefix2.domain.com.  Please check the name and try again."

What do you think?
0
 
MightyMikeyAuthor Commented:
I just discoved that I can ping it by IP but not by domain name.
0
 
MightyMikeyAuthor Commented:
any other ideas?  I cannot change the address that the application connects to, it must connect to the prefix2.domain.com address and not by IP.  Whats wrong with the dns?
0
 
RPPreacherCommented:
Add a zone to your DNS for domain.com
Add an A record to the new zome pointing to prefix.domain.com
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.