Can't access new server via L2L VPN, others are fine.

I have a remote office which connects to us over a lan to lan VPN from a Cisco 506E to our VPN 3000 concentrator.  All is well, except that I have installed a new windows 2003 server to replace an existing 2000 file server, and the VPN users can't access the new shares.  They have a mapping in their hosts file for the new server, but it does not respond to pings or to mapping by name.  The off thing is that they can ping and access the old server which is right next to the new one, and both are plugged into the same unamanged switch.  Everyone in the local office has no problem accessing the new server as well.  

Any ideas where to look?
mchad65Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

amerretzCommented:
Make sure all both networks are using different IP subnet ranges.  I have had this exact problem, it turned out that I was using the same class C address range at both sites. I guess the router still likes something to route.
0
HarsemCommented:
Hello mchad55,

I guess the other thing to check is the subnet mask and the defualt gateway on the new Windows 2003 Server. You have not mentioned if the Windows 2003 Server can access anything else through that Cisco 506E (such as internet or other VPNs).

Alternatively (not knowing your internal network set-up) are you using a static route for the network on the remote site for your Windows 2000 server? You can check this by typing "Route Print" - again, I do not know if that Cisco 506E is your Default gateway or not. If it is not you can add a static route to your Windows 2003 server to point it to the Cisco 506E by typing in a command prompt:

route add 192.168.45.0 MASK 255.255.255.0 192.168.1.1 -p

where 192.168.45 0/24 is your remote network and 192.168.1.1 is the internal IP address of your Pix.

Hope this helps.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mchad65Author Commented:
ugh.  Static routes.  I'll bet real money that's it.  I do have one on the 2000 server.  I forgot all about it.  I won't know until tuesday, as the UK has holidays until then, but that's got to be it.  Excellent.  Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.

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.