• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 153
  • Last Modified:

windws vpn established, but cannot use it for anything.

I've established a vpn connection from a windows xp sp3 box to a windows 7 sp1: the xp side started the connection without problems, and on the w7 side, "network connections" shows "incoming connections - 1 client connected".
I have made the c drive on the W7 side be "shared" and accessible to all authenticated users.
However, I cannot for the life of me figure out how to browse the W7 system from the XP side.  For example, in "my network places" -> add network place " -> "choose another nsetwork place" -> "\\<ipaddress>\c" results in "the folder you entered does not appear to be valid. please choose another".  Likewise "\\<ipaddress>\", "\\<ipaddress>",  and just "<ipaddress>", although error message may vary.

What am I missing?
0
gkoulomz
Asked:
gkoulomz
  • 5
  • 4
  • 3
  • +2
1 Solution
 
John HurstBusiness Consultant (Owner)Commented:
Try the following:

\\<ipaddress>\c$  although you may have to share your Windows 7 drive C for this to work.

\\<ipaddress>\folder where folder is a shared folder on the Windows 7 machine.

... Thinkpads_User
0
 
gkoulomzAuthor Commented:
Thanks for the response, but using "$" didn't help.
I have made the entire c drive a share, just to eliminate this possibility.
I have also disabled Kaspersky firewall.
0
 
John HurstBusiness Consultant (Owner)Commented:
Open a command prompt and type:

NET USE z: \\ipaddress\C$  <enter>  and what error do you get?

NET USE: Z: \\ipaddress\foldershare  <enter> and what error do get?

If you shared the entire drive, use a userid and password and then:

NET USE Z: \\ipadddress\drivesharename  <enter>  and what error do you get?

... Thinkpads_User
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
John HurstBusiness Consultant (Owner)Commented:
@gkoulomz  - Please let us know what happened with respect to the above post and the errors. I have an XP Pro machine connected to my Windows 7 Pro machine right now using Virtual Machines, so it does work. Let us know what errors and we can go from there

... Thinkapds_User
0
 
Rob WilliamsCommented:
You may need to change the firewall configuration on Windows 7 box.  By default when you enable file and print sharing it creates a firewall exception.  However it usually defines the rule as only from the local subnet.  When you connect with a VPN it is considered remote and you have to edit the scope options for file and print share to allow remote subnets.  The easy way to test that is temporarily disable the windows firewall or any others. I kow you mentioned you disabled the Kaspersky one.

As for browsing you usually cannot access through My Network Places as it requires NetBIOS broadcast traffic which is not routable.  You can use the IP as suggested by others, or if you want to connect by name you need to add to the VPN client on the connecting computer the DNS and domain suffix, assuming a domain, as per:
http://blog.lan-tech.ca/2011/05/14/vpn-client-name-resolution-2/
0
 
QlemoC++ DeveloperCommented:
You can also modify your lmhosts and hosts files in %WinDir%\System32\drivers\etc, if you like to use the name instead of an IP address as soon as the firewall is out of the way.
0
 
StiunuCommented:
I assume u have a router in front of your vpn server.
make sure the dhcp class is different from the one on the router.
right click the incoming connection  go to the networking tab select IPV4...tweak  settings.
0
 
Rob WilliamsCommented:
To add to Stiunu's comment:  Presumably the two computers are different sites.  If so the subnet used must be different in every network segment between client and host. If for example the Win 7 and XP sites both use 192.168.0.x you will be able to connect but not access resources. The other site needs to be different such as 192.168.1.x
0
 
gkoulomzAuthor Commented:
Thanks all for your suggestions.  Here are the various responses:

================================================
for thinkpads_user:

C:\Documents and Settings\George>net use z: \\<serverIP>\share
System error 53 has occurred.

The network path was not found.


C:\Documents and Settings\George>net use z: \\<serverIP>\R
System error 53 has occurred.

The network path was not found.


C:\Documents and Settings\George>

C:\Documents and Settings\George>net use z: \\<serverIP>\C
System error 53 has occurred.

The network path was not found.


C:\Documents and Settings\George>
==============================================
for RobWill:
fr Qlemo:
Kaspersky and Windows firewalls are disabled.
Note that on W7 side, "internet connections" shows one incoming connection,
and looking at the detail, there is chatter on the link.

Until I get through, I cannot address the NetBios name mapping issues;
for now, focus is on ip only.

=============================================
for Stiunu:
I do have a router in front of vpn server.
I do not understand "make sure the dhcp class is different from the one on the router.
right click the incoming connection  go to the networking tab select IPV4...tweak  settings. "

=============================================
For Rob Will
This is interesting.  The client side is 192.168.1.*.; the server side
is 192.168.0.*  Normally, the router acts as DHCP in the client side, so
I have no idea how it figured out to use 192.168.1.*. instead of the usual
192.168.0.*.  


For all, output of netstat & ipconfig on client machine:

Client side: (192.168.1.135)
=================================================================
Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:1110         127.0.0.1:3650         TIME_WAIT
  TCP    127.0.0.1:1158         127.0.0.1:1110         CLOSE_WAIT
  TCP    127.0.0.1:1160         127.0.0.1:1110         CLOSE_WAIT
  TCP    127.0.0.1:2541         127.0.0.1:2542         ESTABLISHED
  TCP    127.0.0.1:2542         127.0.0.1:2541         ESTABLISHED
  TCP    127.0.0.1:3402         127.0.0.1:1110         CLOSE_WAIT
  TCP    127.0.0.1:3642         127.0.0.1:3643         ESTABLISHED
  TCP    127.0.0.1:3643         127.0.0.1:3642         ESTABLISHED
  TCP    127.0.0.1:3644         127.0.0.1:3645         ESTABLISHED
  TCP    127.0.0.1:3645         127.0.0.1:3644         ESTABLISHED
  TCP    192.168.0.183:3794     130.117.190.207:443    TIME_WAIT
  TCP    192.168.0.183:3797     38.113.165.86:443      TIME_WAIT
  TCP    192.168.0.183:3800     62.128.100.29:443      TIME_WAIT
  TCP    192.168.0.183:3803     119.254.93.33:443      TIME_WAIT
  TCP    192.168.0.183:3806     119.254.93.36:443      TIME_WAIT
  TCP    192.168.0.183:3809     119.254.93.36:443      TIME_WAIT
  TCP    192.168.0.183:3812     202.177.216.236:443    TIME_WAIT
  TCP    192.168.0.183:3815     62.128.100.43:443      TIME_WAIT
  TCP    192.168.0.183:3818     62.128.100.37:443      TIME_WAIT
  TCP    192.168.1.135:2991     <serverIP>:3389    ESTABLISHED
  TCP    192.168.1.135:3826     192.168.1.1:1780       ESTABLISHED
  TCP    192.168.1.135:36064    192.168.1.1:1780       TIME_WAIT

============================================================================

Windows IP Configuration

        Host Name . . . . . . . . . . . . : Dimension-8300
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
        Physical Address. . . . . . . . . : 00-07-E9-4C-18-A8
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.135
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 167.206.254.1
                                            167.206.254.2
                                            192.168.1.1
        Lease Obtained. . . . . . . . . . : Friday, September 14, 2012 3:09:42 PM
        Lease Expires . . . . . . . . . . : Saturday, September 15, 2012 3:09:42 PM

Tunnel adapter Teredo Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : 00-00-F1-12-BA-8A-EA-44
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 2001:0:9d38:6ab8:0:f112:ba8a:ea44
        IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
        Default Gateway . . . . . . . . . : ::
        NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : C0-A8-01-87
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.135%2
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1
        NetBIOS over Tcpip. . . . . . . . : Disabled
0
 
Rob WilliamsCommented:
Server is 192.168.0.x?  If so good.

It is interesting that there is no traffic reported in the netstat results for port 1723.

To confirm, this is a Windows PPTP VPN?
0
 
gkoulomzAuthor Commented:
Yes, straight windows, if that's what you are asking.  No third party s/w.
0
 
John HurstBusiness Consultant (Owner)Commented:
Windows PPTP VPN?   Yes, straight windows

I wonder if that is the issue.  Windows XP PPRP VPN is different than Windows 7 PPTP VPN. I wonder if they are incompatible. I have not tried this kind of arrangement.

.... Thinkpads_User
0
 
gkoulomzAuthor Commented:
Well, I just got a very surprising result:
Using the vpn server's name (the one that you are told to write down and remember when
you set up the server side vpn), I was ABLE to establish a vpn from the client and map a drive using "net use x: \\svrName\c" !  However, as before, if I use the ipaddress instead of the server name, it FAILS!!

As far as I am concerned, at this point, this question can be closed.

I apologize if I have wasted anyone's time!!!
0
 
gkoulomzAuthor Commented:
And I thank all those who tried to help me!
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now