Recent content by hongjo

Enable IP protocol 47 (Generic Routing Encapsulation—GRE) Port 47 passes tunneled data between the client and the server (including the GRE protocol).

If you have been keeping up with your upates on the Windows 98, there is a good chance you are not using PPTP or IPSec. Cisco and Microsoft developed L2TP which fixes a lot of the shortfalls in PPTP. It runs over UDP port 1701 - try opening that.

What VPN software are you using at each end?

That sounds like your tunnel is terminating at the Linksys and its lan ip address is 192.168.1.100 But I'm confused - why are using explorer and http://, are you trying to connect to a web server? Are you trying to access a web management interface on the Linksys? If not, find any workstation or...

This amy work better: # remote ipfilter append input accept -p udp -dp 1723 internet # remote ipfilter append output accept -p udp -sp 1723 internet It should already let IPSec through, but I should warn you that IPSec does not play well with NAT. If you have NAT (especially at the client end)...

At the command prompt: TYPE attrib *.sys and record the details of what is displayed. TYPE attrib *.ini and record the details of what is displayed. TYPE attrib -r -s -h *.sys TYPE attrib -r -s -h *.ini TYPE copy *.sys a: TYPE copy *.ini a: Now for the fun part, putting the files back the way...

Did you disable the firewall on your DSL router or ICS? ICS comes with a firewall. You need to either disable this firewall or open port 443 for SSL traffic. Personally I would disable the firewall on the ICS connection and turn the one on the DSL router back on and then open port 443.

You have protocols 50, 51 and port 500 open which is what is need for IPSEC, but are you using an IPSec VPN? If it is a PPTP VPN you need to open port 1723.

I'm willing to bet the problem is with NAT. Try plugging the client directly into the DSL and test. If it works, you know for sure it is the NAT causing the problem. NAT and IPSec do not play nice together. Things to try ... First, make sure that NAT-T is enabled on the Cisco and the Tele3. If...

It should work - if you happen to have a share on that system called "sharedresource". If not, substitute the name of a share you do have on the system.

Unless your clients are Windows 2000 or XP Pro (not home), you will also need a Terminal Services license for each of your remote users.