Not yet sire. :smt011So could you get though?VPN Pass-ThroughAllows VPN connections to work through the DI-604.
PPTP
Enabled Disabled
IPSec
Enabled Disabled
I also went in and verified that IPSEC service was started and set to auto.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Not yet sire. :smt011So could you get though?VPN Pass-ThroughAllows VPN connections to work through the DI-604.
PPTP
Enabled Disabled
IPSec
Enabled Disabled
I also went in and verified that IPSEC service was started and set to auto.
Did you foward the port to the correct ip?Not yet sire. :smt011So could you get though?VPN Pass-ThroughAllows VPN connections to work through the DI-604.
PPTP
Enabled Disabled
IPSec
Enabled Disabled
I also went in and verified that IPSEC service was started and set to auto.
Yes sir, port is forwarded to the correct IP. I see now under the vpn host properties general tab, it makes the statement that "no hardware capable of accepting calls is installed." One could argue that would be pertinent if dial up was involved?Did you foward the port to the correct ip?Not yet sire. :smt011So could you get though?VPN Pass-ThroughAllows VPN connections to work through the DI-604.
PPTP
Enabled Disabled
IPSec
Enabled Disabled
I also went in and verified that IPSEC service was started and set to auto.
Me wizard skips the "Devices for Incoming connections." ????
Me wizard skips the "Devices for Incoming connections." ????
I'm gonna try a different machine. It's hard to say what got shut off during the tweaking aka (service disablings) that could be affecting things. :-DMe wizard skips the "Devices for Incoming connections." ????
The ports might be getting screwed up, but your IP and subnet should make no difference. When VPN is connected you'll see your LAN device still with it's normal IP and another device will have an IP from the network you are connected to. You gots junk turned off in your Windows Firewall? You should really get asked, but I've seen it fail before, as I'm sure you have too.On the VPN host machine, I get a response from netstat -an as follows:TCP  library6ptp     66.163.144.**:4541  ESTABLISHED
TCPÂ Â library6:4001Â Â Â Â Â 66.163.144.**:4168Â Â ESTABLISHED
Thats the remote IP. So, it looks like it's trying to get through. Still error 721. It could be due to the fact that the office has a Cisco Pix mapping an internal to a valid external public IP. The internal is on a different subnet than what the host vpn dhcp would hand out however. And if I remember correctly, the port opened for the mapped public was 4001. Dirty Pix. :smt011
I actually disable "Windows Firewall/Internet Connection Sharing (ICS)" on all my machines. I wonder if this would keep the windows dhcp server from allowing the VPN host to assign a IP to the VPN client, since I had dhcp set for incoming connections?ÂThe ports might be getting screwed up, but your IP and subnet should make no difference. When VPN is connected you'll see your LAN device still with it's normal IP and another device will have an IP from the network you are connected to. You gots junk turned off in your Windows Firewall? You should really get asked, but I've seen it fail before, as I'm sure you have too.On the VPN host machine, I get a response from netstat -an as follows:TCP  library6ptp     66.163.144.**:4541  ESTABLISHED
TCPÂ Â library6:4001Â Â Â Â Â 66.163.144.**:4168Â Â ESTABLISHED
Thats the remote IP. So, it looks like it's trying to get through. Still error 721. It could be due to the fact that the office has a Cisco Pix mapping an internal to a valid external public IP. The internal is on a different subnet than what the host vpn dhcp would hand out however. And if I remember correctly, the port opened for the mapped public was 4001. Dirty Pix. :smt011
You should still be able to run DHCP and still assign a static IP to a machine though. One will be static and the rest DHCP, that's the way i run at home.I actually disable "Windows Firewall/Internet Connection Sharing (ICS)" on all my machines. I wonder if this would keep the windows dhcp server from allowing the VPN host to assign a IP to the VPN client, since I had dhcp set for incoming connections?ÂThe ports might be getting screwed up, but your IP and subnet should make no difference. When VPN is connected you'll see your LAN device still with it's normal IP and another device will have an IP from the network you are connected to. You gots junk turned off in your Windows Firewall? You should really get asked, but I've seen it fail before, as I'm sure you have too.On the VPN host machine, I get a response from netstat -an as follows:TCP  library6ptp     66.163.144.**:4541  ESTABLISHED
TCPÂ Â library6:4001Â Â Â Â Â 66.163.144.**:4168Â Â ESTABLISHED
Thats the remote IP. So, it looks like it's trying to get through. Still error 721. It could be due to the fact that the office has a Cisco Pix mapping an internal to a valid external public IP. The internal is on a different subnet than what the host vpn dhcp would hand out however. And if I remember correctly, the port opened for the mapped public was 4001. Dirty Pix. :smt011
I think the office PIX could prove to be insurmountable.Did you ever get your VPN working. I am so excited, i just got my WOL working on my server yaaaaaaaaaaaa!!! :-D