I'm trying to wrap my mind around why this isn't working:
- Fileserver resides in a (virtual) network under a CloudStack VPC 10.1.1.0/24
- Client machine is on a Physical network (also the edge router) 192.168.1.0/24
- There are static routes setup between both subnets and pinging both machines work fine (as well as tracert)
- Windows firewall on the client machine is set to allow "any subnet" for File and Printer Sharing
- Can't find the file share via "\FS" - invalid location
- Ping to "fs" works
- Nslookup "fs" also points to the right address
- VPC rules allow for Egress traffic from 10.1.1.0/24 and both Ingress+Egress from 192.168.1.0/24 (even tried swapping to full allow for both Ingress+Egress)
- Attempting to connect from the physical machine gives this error: "file and print sharing resource is online but isn't responding to connection attempts"
- Attempting to connect from a VM on the same physical network works fine
- IIS on the FS is accessible from all machines including the physical machines
- Same for RDP. Only file sharing is somehow blocked
- tcpdump of the 10.1.1.0/24 interface of the CloudStack router for port 445 shows that the inbound traffic from the physical machine is hitting the router but there is no outbound response. Confirms the error " "file and print sharing resource is online but isn't responding to connection attempts".
- tcpdump shows outbound traffic from the FS to another VM on the same physical network and subnet as the physical machines but all the other physical machines don't get any reply when accessing "\FS"
- Seems like file sharing is being blocked by something. There's some hidden setting somewhere that is causing the file server to discard SMB packets (no outbound traffic on router tcpdump) from outside the subnet. Any ideas where to look?
- I really wish I could use site-to-site VPN but it seems to be broken for ACS
Thanks in advance!
0 Answers