I encountered the following issue regarding the VPN after the last update of SME 7.3 (on 19.Apr.2008):
- I used to connect from my home (Windows XP) to the corporate VPN (which is on SME 7.3) via a standard Windows VPN connection (PPTP); it works fine for more than 1-2 yrs
- after I installed the latest SME updates the VPN connection is done OK, through this connection I can read my email account and the network on SME subnet
The issue:
- when trying to connect a Remote Desktop computer in SME subnet (as I've done before lot of times), when trying to open an MSSQL connection on a database server located on SME subnet (as I've done before lot of times), the SME subnet stop to respond, meaning that Remote Desktop does not connect, SQL cannot be accessed.
I have search a lot the Google/contribs before posting, also I've done some test, but no solution found.
I will explain what test I've done:
- after I connect the SME VPN I open a Windows XP prompt window and I've run the command: PING -T 192.168.2.7 /* this reply continuously the request I've sent to my SQL Server, which is exactly what I want; so far so good */
- I've tried to open Remote Desktop (from my XP) to 192.168.2.7; the Remote Desktop doesn't connected and more than that, ping stops to reply (instead throw timeout expired messages)
- VPN connection looks still connected but actually I cannot browse/access no resource in the SME subnet
- because I wasn't working at all I've closed the VPN connection, reopened again; again, ping -t 192.168.2.7
- now I've tried to open a MSSQL connection (via ADO/OLEDB library, as I've done thousands of times before); the same behavior, ping reply successfully until the SQL connection requested on 192.168.2.7 machine (located on SME network, as I've mentioned few times)
Now, my believe is that when trying to access any resource via VPN tunnel, firewall intercept and DENY the communication.
I've tried these tests on more than one location, trying to test the same VPN/SME server.
Note: SME 7.3 is setup as server/gateway. What I've explained above works just fine until last SME update.
Any ideea? what to check more?
This is not a bug, for sure, that's why I've not reported as a bug, looks like gateway/firewall altered/misconfiguration than an bug.