Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hard Harry]

Ok, did you check if IPsec was on and does it work with your PC in the DMZ? Advanced > Firewall > DMZ host.

[rockets19]

Ok, did you check if IPsec was on and does it work with your PC in the DMZ? Advanced > Firewall > DMZ host.

IPsec was on initially.  I have tried a number of different configuration settings to no avail.  I will enable/disable configuration settings as you and Furry have suggested when I get home.

[Hard Harry]

Yea, if it doesn't work in DMZ, not sure where the problem is. I would suggest Teamviewer at that point and try some trial and error.

[rockets19]

Yea, if it doesn't work in DMZ, not sure where the problem is. I would suggest Teamviewer at that point and try some trial and error.

Okay...

FYI - I did initially put my work laptop's IP addy (as assigned by router) in the DMZ.  Same results.

I am not very router-savvy, despite being in a technology field (software development).  LOL.

[Hard Harry]

Thats odd. Im not sure then. I would have to look at your settings as a whole before I could give any other suggestions.

[rockets19]

Firewall settings for TCP and UDP are both set to Enpoint Indpendent.

IPsec is on.

I have setup a DHCP reservation for my work laptop and included the same IP in the DMZ (the IP as defined by the router - 192.168.0.9).  I attempted a wired login to my work VPN network with the same results.  The logon script was found but errored out after 10 attempts.  I pulled the LAN cable out and attempted via wireless.  Same issue as before.

At this time, I jumped back on the router interface to check the logs.  While looking at other stats, I noticed that two IP addresses were now assigned to the work laptop (guessing the "new" IP was because I went wireless?).  I then added a second DHCP reservation for the second IP for this machine, 192.168.0.7.

I rebooted the laptop and attempted to login wired.  It failed as before.  As soon as the logon script went through it's 10 iterations and then failed, I unplugged the LAN cable for 10-15 seconds and then plugged it back in.

Lo and behold - the logon script finished logging in...successfully.

That's the good news.  The bad news is that I have to unplug and then re-attach the LAN cable after a failed login before it will work wired.  Still no luck with wireless.

Any thoughts?

[FurryNutz]

Are you using zero in the last octet of the IP address? Not sure if this matters or not however generally you don't need any zeros with a single digit number: 192.168.0.9 not .09.

[rockets19]

Are you using zero in the last octet of the IP address? Not sure if this matters or not however generally you don't need any zeros with a single digit number: 192.168.0.9 not .09.

Sorry - my mistake.  Correct - IP contains a single digit in the last octet.

[FurryNutz]

Any interest in having someone review your router settings with you using teamviewer?

[rockets19]

Any interest in having someone review your router settings with you using teamviewer?

I'm almost to that point, Furry...I'm going to try another "test", this time on the VPN side.

The software boots up in Turbo Mode - I am going to turn this off and then try again.  If this works, I am going to remove the "second" IP address for the work laptop (unless any of you suggest leaving it in the DHCP reservation list).

I'll let you know how it turns out.  (later today or possibly tomorrow)

[Hard Harry]

Still not sure why your IT didn't give you a sheet with your login info and network suggestions. Without it we are in the dark.