Windows Explorer (SMB?) Issue

[spencermoore]

Hello all. I'm in the process of implementing a new 5515 ASA, but I'm having an odd issue with Windows Explorer. When the new ASA is in place, we are unable to connect to only one server (DFS server) from our terminal server VLAN. This may not seem like a big issue, but it slows logon times and TS users are unable to connect to shared drives housed on the DFS server etc. I am able to connect from any other server to said DFS server with no issue when the new ASA is in place. I'm confident this is an ASA issue because, for one, I was able to disable ICMP security filtering which allowed me to at least ping the device from our TS VLAN. Secondly, when we revert to the old firewall the issue disappears...I will attach a crude topology for your reference.

Thank you for your help!

[burleyman]

When you say connect to, what do you mean? Are you on the outside through a VPN connection? Are you on the Inside and routing through the ASA? Are you accessing from a site2site VPN?

What are you using to "connect"?

Mike

[spencermoore]

Both servers in question are on the inside. From the TS servers I'm unable to connect to the DFS server via UNC or Run command using \\computername\drive$. Similarly, when users login to the TS servers the drive housed on the DFS server has a red "x" over the drive letter. I was unable to ping the DFS server from the TS servers until I disabled ICMP in the service policy rules section...now I have basic connectivity, but can't access my shares..

[burleyman]

Can you access by \\IP address\Drive$

[spencermoore]

Nope. That failed as well...