New
#31
I haven't changed this (AFAIK) and don't really understand why I would use automatically or a fixed address.TCP/IP4 properties
Optain IP address automatically
Obtain DNS server address automatically
You want to use the remote DNS settings? Unrelated to the problems btw
Client VPN is still 192.168.1.61
do the route -4 print screenshot again. But take screenshot if succesfully connected to vpn server!
Disconnected; reconnected VPN. Route print below
Not that I am aware. PCs have been rebooted a few times in the normal course of things and I am now using a different wifi source (Sky not BTOpenzone - different neighbour!) cos' its a better signal and no drop out after 60 minutes.In #28 I see: 192.168.1.0 255.255.255.0 192.168.1.61 192.168.1.61 26
Bu it isn't anymore in last screenshot. Did you change some settings?
Ping 192.168.1.61 from server (VPN connected) produces 'general failure - Not seen that before!!
Nothing else seems to have changed
Ping 192.168.1.61 from server (VPN connected) produces 'general failure - Not seen that before!!
=>post screenshot of that please.
Can server ping itself, so 192.168.1.67 ?
server: ping 192.168.1.1 ... works?
Answer #38 please
and Troubleshooting General Failure in ping or tracert - Ricky in Melbourne
Virtual Private Network (VPN) - Enable Incoming VPN Connections sure in step 6 tcp/ip v6 is not bound!!!!?
On lcinet the vpn properties isn't bound to tcp/ip v6?
Do not bind the vpn tunnel to tcp/ip v6!