Cisco VPN & Windows File Server

i have customer running Cisco IPSEC Remote VPN to access their file server.
basically, the file server is behind second tier of their corp firewall. 1st tier firewall is belongs to their corp IT and maintenance by them.

my customer owned the 2nd tier firewall, and we just basically permit the VPN subnet to our server LAN. this setup has been works for 3 years and out of the sudden, the VPN users no longer able to access the file server.

if I run telnet to server's port 445, it can go through. only if I run \\ip address of the server, it will prompt error saying the network name no longer available. I have tried by name and IP also returned with same result.

I ran wireshark at the file server it self, and did a telnet from vpn client, I can see there is traffic come in from the client IP with port 445.

Much appreciate any help....
hell_angelEngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

hell_angelEngineerAuthor Commented:
below are 2 logs that I found from firewall rules enabled incoming for VPN client to file server.

6      Aug 16 2016      15:49:02      302021      192.168.100.213      1      10.77.169.1      0      Teardown ICMP connection for faddr 192.168.100.213/1 gaddr 10.77.169.1/0 laddr 10.77.169.1/0

6      Aug 16 2016      15:49:00      302020      192.168.100.213      1      10.77.169.1      0      Built inbound ICMP connection for faddr 192.168.100.213/1 gaddr 10.77.169.1/0 laddr 10.77.169.1/0
JohnBusiness Consultant (Owner)Commented:
I would put Logging on both ends so that when you try to connect, the log will tell you at what point it failed.

Since it was working, there is probably a small setting that changed. But that is hard to know from the description above. That is why I suggests logs, and that is what I do.

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
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
Windows Server 2008

From novice to tech pro — start learning today.