Can't access NAS when VPN'd in to office

[rkorkie]

Hi, I've looked over many of the articles on this site and on google, and many seem to involve similar issues or stories, with the solution somehow being involved with static routes, WINS or DNS. Here is our situation and perhaps someone could point us to the solution without too much guess-work:

We have a Cisco PIX-520 firewall, with a Cisco 2600 router and a Cisco VPN 3000 Concentrator. We are running XP SP2 on our desktops and laptops, and most servers in the office are running Windows 2000 or 2003 server. When we are in the office hard-wired to the gigabit LAN, we can ping and access any share on any machine, including our Snapserver 520 NAS box. This Snapserver runs Guardian OS 4.1.061. We are running a WINS and DNS server in the office, and all machines are configured, including the NAS server with IP 192.168.50.69.

When at home with our laptops, we use the Cisco VPN client 4.8.01.0300 to connect to the office. We can ping and access every windows machine, but we cannot access the NAS Snapserver, nor can we ping it. It does not respond in any way. We have "allow LAN access" check in the Cisco VPN client. We have NetBIOS enabled on the laptops.

I've read that maybe static routes or configuring something on the Cisco router could be a fix, but seeing as we aren't all that adept to this type of networking, we don't really know what we are to do as a previous IT set all this up for us and is no longer available. Any direction or suggestions are greatly appreciated.

Ryan

[chicagotech]

Can you ping the NAS by IP?

[rkorkie]

No, it is not pingable by IP when connected via VPN from remote location. But when in the office, yes you can ping it by IP. Does that help narrow it down?

[chicagotech]

What's the LAN IP and remote site IP?

[rkorkie]

The LAN ip of the NAS is 192.168.50.69. All machines on the LAN are in the 192.168.50.xxx subnet. When VPN'd in, the IP address of the Cisco VPN adapter is 192.168.30.xxx

Just as a reminder, all other machines can be pinged by IP or dns name when on the LAN or when VPN'd in.

[chicagotech]

You may want to use tracert command to find out where the traffic go and stop.

[rkorkie]

I ran the tracert 192.168.50.69 from my remote location while VPN'd in, and all I got was ping times for host2.sustain.net [63.79.230.2] which is the external IP and then there were no further hops - all "request timed out" responses.

When we did a tracert to another machine (192.168.50.64), we got 2 hops and the tracert was succesfully completed:
1) host2.sustain.net [63.79.230.2]
2) blade7.denver.sustain.net [192.168.50.64]

Not sure where the holdup is based on those results if it will work many machines but excludes a single one. Feedback appreciated.

[chicagotech]

post back with the routing table here may help.

[rkorkie]

To be honest, I'm not even sure exactly what that is (though I have an idea), or where I'd go to get it and what command I would type to retrieve it. Is this something you could explain in a couple sentences or less?

[chicagotech]

These pages not noly provide information how to get routing table but also how to troubleshoot.

Routing
However, if this is the case, what you may do is modifying the routing table manually and accordingly. For the consultants, refer to case 121504RL. ...
http://www.chicagotech.net/routing.htm

routing - how to
How to display the routing table How to disable ip routing/forwarding on a W2K Pro? How to enable ip routing/forwarding on Win2k ...
http://www.chicagotech.net/routinghowto.htm