User could not connect from the DC office to the Baltimore Office server’s shared folders
User's PC and network are on a subnet 192.168.3.1 connected to the Baltimore network 192.168.2.0 thru a VPN
- The VPN is working fine. I was able to ping to the server (192.168.2.2) and the router at 192.168.2.1 from 192.168.3.1 (the remote location’s router) and I was able to ping from Julia’s PC on subnet 192.168.3.0 to any device on 192.168.2.0 – and vice-versa
The server is a “Windows Server 2003 R2” with all the latest service packs and updates
- The Firewall was enabled.
- When I would disable the Firewall, there are no issues connecting to the shared resources on the Baltimore server from DC
Re-enabled the Firewall and performed the following
I modified the setting in the “Windows Firewall”
Clicked “Exceptions tab”
Clicked “File and Print Sharing”
Clicked on the already checked “TCP 139” and then clicked “Change Scope”
In the “Custom list”, I then added this entry - 192.168.3.0/255.255.255.0
I now can connect to Baltimore from the DC office with no issues
- Did I pick the correct settings by adding a custom port for TCP 139
- Should I do anything for these ports?
Any help and suggestions would be appreciated