New
#11
1. Teamviewer -Sure. No problem. You want another IPCONFIG?
Problem sysmptoms are the same as before Teamviewer (and LogmeIn) tried.
Also tried OPENVPN which nearly worked :-(
2. IPCONFIG /ALL > file.txt
1. Teamviewer -Sure. No problem. You want another IPCONFIG?
Problem sysmptoms are the same as before Teamviewer (and LogmeIn) tried.
Also tried OPENVPN which nearly worked :-(
2. IPCONFIG /ALL > file.txt
Please uninstall logmein, teamviewer vpn and openvpn please. Then reboot. Same on server.
use win7 vpn server on the server. How to Set up an incoming VPN on Windows 7
or better How To Setup VPN on Windows 7 as Home Solution - YouTube first 1:30 minute.
on client do video from 3:09
What is the public internet address of vpn server? Connect to that ip number from client.
--------------------
Give me any errors/problem you have. Post ipconfig output of client and server, after successfully connecting to vpn
On both machines:
- Openvpn and LogmeIn are long gone.
- Teamviewer now gone.
- reboot done as matter of course.
Windows 7 vpn server set up.
Port 1723 opened on TPLINK 89780 router and checked with PFPortchecker . PPTP enabled
VPN set up using tutorials on sevenforums (4518 and 4517) I looked and they settings all look kosher. You want me to do this again?
Client connected. Server reports incoming connctions 1 client connected
Client computer reports Work network - no internet connection.
Disconnect VPN
Unhook client from LAN
Activate Wirelss connection to BTinternet
Log on to BTinternet.
Activate VPN which says it connects fine.
Server shows incomoing connection
Client shows work network connection through VPN with No Internet Access.
Can ping the server from client by IP or name
Reply from 78.86.160.148: bytes=32 time=60ms TTL=52
But cannot access the server by name or IP.
Map network drive->browse shows local drive only
Map network drive to \\78.86.160.148\share produces attempting to connect . . . and then "cannot access"
"network Diagnostic" goes on to say: Computer corectly configured but device (IP) is not responding
ping 78.86.160.148
and
\\78.86.160.148
accesses the remote router, not the vpn server! So you're connect succesfully.
Post ipconfig/all output again please
Virtual Private Network (VPN) - Enable Incoming VPN Connections step 6.
Post what you entered in this screen:
Thanks for your continued assistance
Ping 78.86.160.148. does indeed access the router. Not clear at all how I might ping a PC on the other side of the router?
Ping the PCs LAN address produces 'no reply' - hardly surprising
Ping the PCs name produces 'cant find pcname'
Step 6 is set up exactly as the picture
Tick allow callers; Check assign IP automatically
No tick Allow calling computer.
Worrying that the VPN describes itself as a public network. Thought it was supposed to be work. I can (and do) change it but . . . . . still no Internet Access. Still no access to server files.
IPCONFIGs follow
CLIENT
Windows IP Configuration
Host Name . . . . . . . . . . . . : R60
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
PPP adapter Hewitt VPN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hewitt VPN
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.61(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address. . . . . . . . . : 00-19-D2-98-12-AD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::29f1:c508:71a2:fe30%11(Preferred)
IPv4 Address. . . . . . . . . . . : 10.150.14.146(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Lease Obtained. . . . . . . . . . : 05 March 2014 00:30:32
Lease Expires . . . . . . . . . . : 05 March 2014 00:45:32
Default Gateway . . . . . . . . . : 10.150.14.145
DHCP Server . . . . . . . . . . . : 10.150.14.145
DHCPv6 IAID . . . . . . . . . . . : 167778770
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-5D-DD-31-00-16-D3-B9-92-6B
DNS Servers . . . . . . . . . . . : 192.168.22.22
192.168.22.23
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-16-D3-B9-92-6B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{BD39B3AB-E5D5-4B98-B418-B1590DA03948}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{BD862C31-01F0-4F42-9313-D5984349AEA6}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{89537055-7619-45E2-9BBC-010DBECF4CAC}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
SERVER
Windows IP Configuration
Host Name . . . . . . . . . . . . : Ponder
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
PPP adapter RAS (Dial In) Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : RAS (Dial In) Interface
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.61(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 00-22-FA-D8-C1-5F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-22-FA-D8-C1-5E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connection
Physical Address. . . . . . . . . : 00-23-18-96-E4-41
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.67(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 9:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:439:1de8:b1a9:5f6b(Preferred)
Link-local IPv6 Address . . . . . : fe80::439:1de8:b1a9:5f6b%25(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{6E06F030-7526-11D2-BAF4-00600815A4BD}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{6C11DF96-CAF9-4217-9FFD-E178A7E26AFC}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Intel(R) PRO/Wireless 3945ABG Network Connection
10.150.14.145
=>That's not the same client as before! How can I compare and give advice if you do so
"allow callers to access my local network". Why did you put a checkmark there? I thought you only want access to the vpn server itself(?)
Sorry about the Intel(R) PRO/Wireless 3945ABG Network Connection
10.150.14.145.
When testing the VPN client I remove it from the LAN and log onto a local wireless connection. However, the connection is not great and transfer speeds are pretty slow so mostly unless testing I am hooked to the LAN and the wireless is not operating.
Allow callers . . . . Seemed like a good idea at the time.
Client side has subnet: 192.168.1.*
Server side has subnet: 192.168.1.*
Client doesn't know where 192.168.1.18 is for example.
------
All computers on client side are using dhcp? router on client side has no port forwarding, dmz.... no special things? No applications on any computers connected to client side router use "hard coded" ip numbers? If all is true:
change client routers ip address to 192.168.x.1 for example 192.168.20.1 (but not 192.168.1.1!) Router will reboot automatically after changing, if not... reboot it. After that restart all computer connected to router. Or do "ipconfig/renew all" on all computers from elevated command prompt. Post back when done