Plusnet: Stop blocking my incoming VPN connection.

[#1]

---

@7up wrote:
Who said I've got common ports open? - you can redirect external ports to different ports inside the network as I have for incoming rdp connections.

---

That should be the other way round……

[#2]

I shouldn't have to put up with that, I changed nothing!

Yes you shouldn't, but stuff happens, perhaps a fault has occurred rather interference from an outside source.

If you think it's the router try another one.

Are you running an up to Windows system nothing no longer supported?

[#3]

---

@Champnet wrote:

---

@7up wrote:
Who said I've got common ports open? - you can redirect external ports to different ports inside the network as I have for incoming rdp connections.

---

That should be the other way round……

---

So you're saying I should accept rdp connections on 3389 and route them to an internal port that is different?

Cos I was accepting them on an external port different than 3389 and directing them to the internal 3389 port where the RDP server is listening. That makes more sense to me.

[#4]

You wrote :

"Who said I've got common ports open? - you can redirect external ports to different ports inside the network as I have for incoming rdp connections"

I read that as standard external ports redirected to non standard internal ports, my apologies......

[#5]

@7up nobody is doing anything remotely and as previously advised, there have been no recent software updates for the hub. I don't know why the behaviour has recently changed, however the trigger is likely closer to home - whether there are firmware bugs or not.

---

@7up wrote:

@bobpullen this was NOT me - just seconds ago..

I'm in the router right now and see no unknown devices connected. That means it's got to be coming from somewhere.

If it's not me and it's not anybody else local.. 

Care to explain?

---

Is the VPN running on port 4500? Isn't this just an indicator of the behaviour you described where a 'bad' port forward association gets reverted to a 'good' one after a period of time with no VPN client devices connected?

I guess the bridged adapters could also be contributing to the problem. Only way to determine that would be to try removing the bridge temporarily to see if it makes any difference.

As mentioned, I'm not familiar with the native Windows VPN server but is there a way to have it assign VPN clients IP's that are outside of the LAN subnet e.g. use 10.8.0.x IPs?

[#6]

I guess it could assign those ranges but I have a vague memory of trying that previously and then my phone couldn't access the PC's services (FTP, apache etc). Can't remember now but I settled on the current setup a long time ago and it just worked - faultlessly.

I don't think it's the software adapters / bridge, it's worked well for years.

As for port 4500, that was originally a port I added out of desperation as google said that L2TP uses that port aswell as those in the 17** range. I'd never needed it before and after adding it, I got blocked again so I deleted it.

Moment later, the tech log on the router shows its been added again - but mentioned nothing about it being deleted until I deleted it a 2nd time.

The bad port forward you mention that I touched on, was actually a bad IP address forward. Again, the router picks up the IP of the device that's connected via VPN and then it decides that IP is for the PC and tries to forward traffic to that instead. As the router has blocked the device connecting, it is in essence, forwarding traffic to a device not on the network. After X time, the router gives up on that and then reverts back to the PCs real IP.

Not that any of this matters now, I've give up on remote VPN access now. The change of IP address and it suddenly working said everything.

Moderators Note: Full quote of preceding post removed, as per Forum rules