Can not access the Lan after I connect with a cisco vpn client

[sisip]

I have a pix 501 firewall. In the pix configuration, I configured the address-pool with the local pool name. I also configured the pix to connect to a radius server on a Domain Controller with advance server. The active directory on the advance server is enable.
The clients connects to my domain with the VPN clients version 3.6 with their original LAN username and password with no problems. The problem is that they can not browse and ping the LAN network. They can not access anything on the network.
Any idea. Is it the DNS on my Windows domain?

 

[MattWray]

Have you run an IPCONFIG once connected to verify that you are recieving an IP for your network?

Thanks,

Matt Wray
MCSE, MCSA, MCP, CCNA

http://www.sss-steel.com

http://www.total-tec.com

 

[ChicagoTechNet]

Have you added DNS and WINS into the PIX? Quoted from

http://www25.brinkster.com/ChicagoTech

How to add DNS and WINS into your Cisco VPN server

If your VPN client cannot find servers or cannot ping computernmae, you may need to add DNS and WINS into your VPN server. For example, to add DNS and WINS on a Cisco Firewall PIX, add vpdn group 1 client configuation dns dnsservername and vpdn group 1 client configuration wins winsservername.

For more information, go to

http://www25.brinkster.com/ChicagoTech

Robert Lin, MS-MVP, MCSE and CNE
Windows & Network Support, Tips and FAQs on

http://www25.brinkster.com/ChicagoTech

 

[sisip]

Yes. I had the DNS and WINS and address from my Domain Controller. The VPN Dialer client had the ip address that came from the pix address-pool. In the ipconfig /all command there was no DHCP address.
Thank you for your help

 

[sisip]

Thank you Robert Lin,

I have a vpngroup configured to the DNS and WINS server. Is there a difference with vpnd group.

Denis

 

[ChicagoTechNet]

post the result of the vpn client's ipconfig /all may help.

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network and How to at

http://www25.brinkster.com/ChicagoTech

 

[northstardave]

Is the pix the default route out of your LAN? I had a similar problem caused by my servers not having a route to the VPN clients through the pix. i.e. the Default route was a different box & so nobody could find things on the VPN.

Did that make sense?

 

[sisip]

Thank you for your response Northstar Dave.

Last night I verified and you were right. They were going out on the router instead of the Pix. I changed it and it still does not work. When a client connects to the pix, it connects immediately and he is authenticated immediately also. To my knowledge, he should be on the network since the authentication is done on my NT 4.0 PDC. The client still can't see the network and they still can't ping internal ip addresses, not even the ip of the nt4.0 PDC. I think it a configuration in my Pix. Do you think I am right?
Thank you

 

[Shift838]

This is a feature of the CISCO VPN client. It is the way it is written. Once the CISCO is activate it cuts off access to your LAN/WAN unless you have your entire network accesible via the internet which is very unlikely.

 

[sisip]

I want to thank everybody who tried to help me. It finally works. My NAT configuration in the pix was wrong.


Thanks to everyone