Checkpoint with SBS 2003 connection issue

[JonD]

Up until recently I have had really good success connecting to work stations in a domain on an SBS 2003 server. For some reason I can no longer connect when the work station is connected to the server.

Their Checkpoint router is somehow affecting the connection (It was updated recently).

If I use Crossloop I can connect although the performance seems to be slower.

See solution to this issue later in this thread.

JonD

[supercoe]

For some reason I can no longer connect when the work station is connected to the server.

Do you see the ID number show up in the repeater log?


There must be something different about how Crossloop connects and Chunk VNC connects.

AFAIK Crossloop uses TightVNC which in my experience handles slow connections better.


Sounds like it's possible to place the blame on the updated router at this point in time.

[JonD]

I'm using a Linux repeater... not sure about the logging. I will have to check my repeater computer to see if it does log.

Here's what I have done:
1. user logs in to domain account (off-line from server)... no vpn
connection
2. we connect successfully with ChunkVNC
3. we disconnect and do the usual uninstall
4. they connect to server over VPN
5. we try the ChunkVNC connect and it fails

To eliminate the possibility of the VPN being the culprit, I attempted a
connection with a user in the office (no VPN). I used to be able to
connect but this also fails.

I have "tweaked" ChunkVNC but have had no other issues. I'll give
it a try with the original version just to be sure.


EDIT:
I wonder if switching the server port to 443 would be worthwhile?
I'm just wondering if their router is blocking other outgoing ports.

JonD

[JonD]

Well I've got to the bottom of the problem. It would appear that their
CheckPoint router is being very protective. It may apply to other overly
protective routers.

What I think happens:
1. I frequently VPN into their server to do admin work
2. The router puts my IP address in the cache and marks it as an incoming connection
3. Later, when a user on their network wants to connect to my Chunk
server, the router blocks the connection because it is an outgoing
connection to an IP address that was previously used for an incoming
connection.

When I'm away from the home base, the above will not happen as my
incoming connection over the VPN for server admin will be from a
different location (IP address) than my Chunk server... but, before I
leave the home base the following solution needs to be applied.

Solution
After using the home location for VPN server administration, always get a
new IP address by rebooting the router or modem before trying Chunk
server support.

Hope this helps someone else

JonD