Search results for query: *

ok i think this will work can i get the port ranges for IPSec and if it is UDP TCP or TCP/UDP L2TP and if it is UDP TCP or TCP/UDP PPTP and if it is UDP TCP or TCP/UDP then i open all those ports and that will cover all my bases for hte vpn yea?

wow should have taken a look at the log long time ago. this should help Mon, 12/04/2006 11:52:49 - TCP connection dropped - Source:xxx.xxx.xxx.xxx, 17898, WAN - Destination:xxx.xxx.xxx.xxx, 1723, LAN - 'Suspicious TCP Data' the desitination is my sever ip address and the soruce is my remote...

Im not sure what you mean by rule...I have a service added for VPN on port 1723 TCP and that port is fowareded to my server. There is not NAT. Remote host connects to my WAN...Static IP. And im prety sure there IPSec just the defual windows vpn.

Well I thought I was in the clear but another problem has arose. I was forced to clear the firmware on my router (FVS318) Netgear Firewall Router and so I ran into some problems. This is a vpn router but i do not use the vpn i simple use windows incomming connection. But i needed to foward...

hey um the VPN host was just an incomming connection and a win 200 sever and the client was just a vpn connection in netwrok connections....but the trick was i couldnt alter the routers in any way on either side....unfortunatly i had to take drastic measures and was forced to bring down 3 remote...

So my network with the server that im connecting to has the ip range of 192.168.1.XXX and the network that I am VPNing in from has the same IP range 192.168.1.XXX. So the computer with the VPN doesnt go to the VPN it stays within the local network and I cant connect. Ive been trying to add a...