I've recently started migrating our companies file server from Novell onto Server 2008, everything's working ok apart from mapping drives via VPN.
I've created a login script to run after the VPN connection is made and the script itself works fine when I'm connected to the network. When I'm connected via VPN to the network however I get the 'network path not found' error.
We have a very strong corporate firewall (which i have i no control/management of) so I assumed additional ports needed to be opened on the firewall. After talking to the firewall guys and getting various ports opened with no result I requested they create an 'any rule' allowing any traffic from my VPN IP to the Windows File Server (for testing only)
However I'm still getting the 'network path not found' error and am unable to telnet to the server on various ports. Can't ping the server etc.
The Windows Server 2008 firewall itself is completely disabled.
When connected on the internal network I can:
Ping the server
Telnet on: 139, 445, 3389, 48778
Map drives fine via UNC path or Login Script i created.
Over VPN since the any rule was put in I can:
Resolve IP via ping but the actual request times out.
Telnet on 3389 & 48778 (Trend Micro port)
RDP into the File Server.
Can anyone think of anything i might be missing? Any more information you need?
A colleague of mine is a linux nut and he explained that while the local firewall is open the service itself might only accept connections from a certain subnet etc. ie. the file sharing service or whatever that listens on 445 may only accept connections from the same subnet as itself.
I've never heard about this in windows, is this a possibility?
I've done a netstat -a and pasted it in the code section below after removing any established connections.
The corporate firewall is apparently showing no blocked ports in logs, searching through the VPN logs we can see alot of connections trying to be made on ports 80/8080/524 and RST ACK are sent back but nothing on any file sharing ports.
wfs01 is the filesever and has a 172.19.12.6 IP. When i come in over VPN I am given 192.168.103.176, but RDP is working so the NATing is ok?
TCP 0.0.0.0:111 wfs01:0 LISTENING
TCP 0.0.0.0:135 wfs01:0 LISTENING
TCP 0.0.0.0:445 wfs01:0 LISTENING
TCP 0.0.0.0:1039 wfs01:0 LISTENING
TCP 0.0.0.0:1047 wfs01:0 LISTENING
TCP 0.0.0.0:1048 wfs01:0 LISTENING
TCP 0.0.0.0:1581 wfs01:0 LISTENING
TCP 0.0.0.0:1688 wfs01:0 LISTENING
TCP 0.0.0.0:2049 wfs01:0 LISTENING
TCP 0.0.0.0:3389 wfs01:0 LISTENING
TCP 0.0.0.0:5357 wfs01:0 LISTENING
TCP 0.0.0.0:48778 wfs01:0 LISTENING
TCP 0.0.0.0:49152 wfs01:0 LISTENING
TCP 0.0.0.0:49153 wfs01:0 LISTENING
TCP 0.0.0.0:49154 wfs01:0 LISTENING
TCP 0.0.0.0:49155 wfs01:0 LISTENING
TCP 0.0.0.0:49193 wfs01:0 LISTENING
TCP 0.0.0.0:49208 wfs01:0 LISTENING
TCP 0.0.0.0:51238 wfs01:0 LISTENING