If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.
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....
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....
Asked:
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.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
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