Desktop (DESKTOP) with Vista (64 bit) Home Premium is set to accept incoming connections via VPN. (Configured in TCP/IPv4 for Server:192.168.0.131) and Client:192168.0.132).Laptop (LAPTOP) with XP Home is set as VPN Client. LAN/WAN DLink DI-624 router is set handle PPTP on 1723 and GRE 47. DESKTOP is static DHCP: 192.168.0.131. This router is assigned a dynamic IP through the ISP. I am using dyndns hostname to connect to this router via the client.File sharing works fine between two systems over LAN with and without the VPN connection. Over LAN, Hostname DESKTOP or 192.168.0.131 can be used via client to connnect to server. File sharing does not work from a remote VPN connection. This is the problem I need solved. NOTE: Software firewall was disabled on DESKTOP and LAPTOP for all the tests described in this post.XP Client connects remotely via WAN to Vista Server over a Linksys WRT54G set to pass PPTP. Hostname = DynDNS_hostname allows the connection. Vista Server shows Client Connected. Is this the correct hostname? It seems this is the name of the Dlink router and not the Server? However, I have tried various combinations which do not authenticate. PPTPSRV and PPTPCLNT tests verify connectivity. HOWEVER this works only with PPTPCLNT 192.168.0.131 AND DOES NOT WORK with PPTPCLNT DESKTOP. Is this a clue?Laptop does connect successfully to the internet during the VPN Connection.Client Laptop VPN Connection Status\looks normal with correct Server/Client Addresses (...131 and ...132), MS CHAP V2 Authentication (MPPE 128 encyption), Server Type PPP, Transports TCP/IP.Server VPN Connection Status shows: IPv4 and IPv6 NOT CONNECTED. Media State CONNECTED. Is this correct or is this a clue?I also tried mapping the shared folders, but that didn't work either.I cannot view the DESKTOP Shared files with the remote VPN Connection from the client. I read about 100 posts on this and cannot seem to resolve the issue. Any thoughts on what I am be doing wrong would be sincerely appreciated.

When I try to acces the shared drive remotely byentering the path in IE7, the run command, or from My Network Places, I get the following error: \\Desktop\f is not accessible. . . The netowrk path was not found.

Hi Corky, Please refer to the following steps to resolve the issue: 1. On Windows Vista, created a loopback adapter and assign it an IP in the same subnet as the PPP adapter. 2. Access the share with the IP address of the loopback adapter. Hope it helps. Sincerely, Joson Zhou Microsoft Online Community Support

The LAN addresses are 192.168.0.XXX. I have assigned a static IP Address toDESKTOP Ethernet Adapter 192.168.0.131 The PPP adapter RAS interface shows an autoconfig IPv4 Address of 169.254.0.xx and no physical address. After connecting the client to the VPN, the server's client connection statusshows IPv4 NOT CONNECTED, IPv6 NOT CONNECTED, Media State CONNECTED. The Client's Connection Statusshows it is connected to the server at 192.168.0131, server type PPP (and other details given in the orignal post. It appears that while the client connects, it cannot access the shared resources. I created a loopback adapter as you can see below from the ipconfig details. I am unsure of what you are asking that I do with respect to assigning the IP to the loopback adapter because of the different subnets shown above. C:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Desktop Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : xxxxxxxxxxxxxxxx Ethernet adapter Loopback: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Loopback Adapter Physical Address. . . . . . . . . : 16-09-25-04-00-51 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 169.254.0.51(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter xxxxxxxxxx: Connection-specific DNS Suffix . :xxxxxxxxxxxxxxxxxxxx Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-E0-4D-20-66-35 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::e5ff:822c:99b6:b449%7(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.131(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Sunday, February 24, 2008 1:32:29 PM Lease Expires . . . . . . . . . . : Sunday, March 02, 2008 1:32:29 PM Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 184606797 DNS Servers . . . . . . . . . . . : 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled PPP adapter RAS (Dial In) Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : RAS (Dial In) Interface Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Autoconfiguration IPv4 Address. . : 169.254.0.18(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter Local Area Connection* 10: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

Hi Corky, Here are the detailed steps: ============== 1. Based on the IP address assigned to the PPP adapter (169.254.0.18), I notice that there is no DHCP server in the local environment. In this case, I suggest specifying the scope of IP addresses for the incoming connection. Please refer to the following steps:1) On the Windows Vista machine, double-click the incoming connection, and select Networking tab.2) In Network components section, select Internet Protocol Version 4 (TCP/IPv4), and click Properties.3) Under IP address assignment, select Specify IP address and type the scope of IP addresses for the incoming connection. For example, from 192.168.3.1 to 192.168.3.3. 2. After the Windows XP laptop make the VPN connection to the Windows Vista machine, you should find that the IP address of the PPP adapter RAS (Dial In) Interface on the Windows Vista machine is 192.168.3.1, and the IP address on the laptop should be 192.168.3.2 (or 192.168.3.3). 3. After that, please manually assign IP address 192.168.3.4 to the Microsoft Loopback Adapter on the Windows Vista machine. 4. Access the share resources on the Windows Vista machine with the IP address 192.168.3.4. For example, \\192.168.3.4\share. Hope it helps. Sincerely, Joson Zhou Microsoft Online Community Support

Let's use actual IP Addresses to avoid any misunderstanding on my part. 1-4 below correspond to items 1-4 in your last post. 1. IP Addresses are assigned and functioning (see original post.) 192.168.0.131 is the Vista Server (DESKTOP) 192.168.0.132 is the XP Client (LAPTOP) Originally, I had the above two addresses in the range. however, I changed it to 131 through 143 and the behavior is exactly the same. These are confirmed when the VPN Connection is made on the LAPTOP and I view the status. 2. The PPP Adapter on the Vista Server still shows 169.254.0.20 after the VP Connection is made (maybe this is the problem). 3. I assigned 192.168.0.133 to the Loopback Adaptor 4. Cannot connect to either \\192.168.0.131\Desktop or to \\192.168.0.133\Desktop _________________ Once the connection is made, the status of the connecton on the Vista Server shows IPv4 Connectivity NOT CONNECTED Media State:Connected Any other thoughts?

Hi Corky, Yes, the problem should be that the PPP Adapter automatically get an APIPA address 169.254.0.20. As a result, I suggest specifying the scope of IP addresses for the incoming connection as I referred in the previous post. For your convenience, Ive included the steps in my last post as below: 1) On the Windows Vista machine, double-click the incoming connection, and select Networking tab.2) In Network components section, select Internet Protocol Version 4 (TCP/IPv4) and click Properties.3) Under IP address assignment, select Specify IP address and type the scope of IP addresses for the incoming connection. For example, from 192.168.3.1 to 192.168.3.3. Please understand that the IP address of PPP Adapter is assigned from that scope. If you select Assign IP address automatically using DHCP but there is no DHCP server available, the PPP Adapter will get an APIPA address such as the 169.254.0.20. I cannot fully understand point 1 in your post. Do you mean that the IP address 192.168.0.131 is configured in that scope and it is assigned to the Ethernet Adapter? I look forward to your reply. Sincerely, Joson Zhou Microsoft Online Community Support

Joson:Understanding point 1 in my last point is very important. Here is another explanation. Yes, I am already have beenassigning the range of addresses as you suggested. I assigned the range 192.168.0.131 to 192.168.0.132.This is shown in my original post. I can check after the client-server connection is made that the range was properly assigned as I have in the above posts. After reading your last suggestion, I assigned the range 192.168.0.131 to 192.168.0.143. With either range, the PPP Adapteris automatically being assigned169.252.0.xx. For some reason the adapter is not being assigned an address from the from the range 192.168.0.131 to 192.168.0.143. Now, I have tried again. I assigned the range 192.168.0.131 to 192.168.0.133. The. PPP Adapter is still shows 169.252.0.xx afterwards. It looks like this may be the problem. . . where the APIPA Address is being assigned even when we specify astatic addresses pool.. Please see: http://forums.techarena.in/showthread.php?t=897073

Corky10 wrote: Joson:Understanding point 1 in my last point is very important. Here is another explanation. Yes, I am already have beenassigning the range of addresses as you suggested. I assigned the range 192.168.0.131 to 192.168.0.132.This is shown in my original post. I can check after the client-server connection is made that the range was properly assigned as I have in the above posts. After reading your last suggestion, I assigned the range 192.168.0.131 to 192.168.0.143. With either range, the PPP Adapteris automatically being assigned169.252.0.xx. For some reason the adapter is not being assigned an address from the from the range 192.168.0.131 to 192.168.0.143. Now, I have tried again. I assigned the range 192.168.0.131 to 192.168.0.133. The. PPP Adapter is still shows 169.252.0.xx afterwards. It looks like this may be the problem. . . where the APIPA Address is being assigned even when we specify astatic addresses pool.. Please see: http://forums.techarena.in/showthread.php?t=897073 This problem with the PPP Adapter referred to in the above article (link)is explained in KB928233. I applied the resolution to the network adapter and not to the PPP Adapter? Should I have applied it to the PPP Adapter. The other thing that I have found out is that 192.168.0.133 is being assigned. It is assigned to the Loopback adapter and not to the PPP Adapter. The problem remains with the PPP Adapter getting the APIPA Address. Thank you for mentioning the APIPA address issue because I then looked up APIPA Address which led me to finding there is a known problem. However, I still have not resolved the problem. Thanks.

Hi Corky, I think I have found out the cause: the IP address assigned to the Ethernet Adapter is included in the IP pool, which result in the PPP Adapters inability to get IP address from the pool. Please follow the following and configure the IP address as I refer in the steps to check the result: 1. On the Windows Vista machine, specify the scope of IP addresses for the incoming connection:1) On the Windows Vista machine, double-click the incoming connection, and select Networking tab.2) In Network components section, select Internet Protocol Version 4 (TCP/IPv4), and click Properties.3) Under IP address assignment, select Specify IP address and type the IP address as below: From: 192.168.3.1 To: 192.168.3.3 2. After the Windows XP laptop make the VPN connection to the Windows Vista machine, you should find that the IP address of the PPP adapter RAS (Dial In) Interface on the Windows Vista machine is 192.168.3.1, and the IP address on the laptop should be 192.168.3.2 (or 192.168.3.3). 3. After that, please manually assign IP address 192.168.3.4 to the Microsoft Loopback Adapter on the Windows Vista machine. 4. Access the share resources on the Windows Vista machine with the IP address 192.168.3.4. For example, \\192.168.3.4\share. Hope it helps.

Thank you for your efforts. I have already done steps 1 and 2. as you suggested, and the PPP adapter does not get the address from the pool.

Hi Corky, I appreciate the time and effort you invested on this issue. To better understand the issue, please export the IP configuration of both the Windows Vista and Windows XP machines after establishing the VPN connection.

Hi, had the same problem as discribed before. But I can access the shares by using the IP address. Question is, why is the connection not behaving the same as when I am home connected to the network? I can't see any of my other machines in the network. I want to be able to access my files on the other machines. Any thoughts? Thanks, Suresh

I'll try my question here because this is the post that I used to setup our VPN and file sharing following the directions here. In our case, we have a VPN server running Server 2008 in a domain environment. The clients that connect do so solely to access files that reside on the VPN server itself, but the clients that connect are not in the domain and have different username/passwords than their domain accounts. This is the cause of grief.Here is the setup:Windows Server 2008 (VPN Server)Ethernet adapter 1: public ip addressEthernet adapter 2: 192.168.4.1 (enabled only for testing later)Loopback adapter address: 192.168.211.1VPN address range: 192.168.211.2-192.168.211.311. When you connect to the VPN Server via \\192.168.211.1, it allows the client to view all the shares.2. If you try to open any share, you get an "Access is denied" message and no prompt to enter new credentials.3. If you then try to map a network share with different credentials, you get a warning saying you cannot connect to the same machine with multiple credentials.The key to this whole problem is item 1. If you directly connect the computer via an ethernet cable, once you attempt to connect to \\192.168.4.1\, you are immediately required to authenticate with valid credentials. The server will not list all of the shares and such like it does when you connect via the loopback adapter/VPN server. This makes me think that the loopback adapter is somehow treated differently or some such thing, but I haven't been able to track it down.In order to connect to a file share on the VPN server one must first map a network drive with the different domain credentials before accessing the \\192.168.211.1 computer/share. This solution works, but it is very un-user-friendly.This isn't a firewall or security permission problem because it is off and the permission are set to Everyone with Full Control and the NTFS permissions are the same.Local Security Policy settings (not overridden by Group Policies)Network access: Allow anonymous SID/Name translation - DisabledNetwork access: Do not allow anonymous enumeration of SAM accounts - EnabledNetwork access: Do not allow anonymous enumeration of SAM accounts and shares - EnabledNetwork access: Let Everyone permissions apply to anonymous users - DisabledNetwork access: Named Pipes that can be accessed anonymouslyNetwork access: Restrict anonymous access to Named Pipes and Shares - EnabledNetwork access: Shares that can be accessed anonymously - Not DefinedNetwork access: Sharing and security model for local accounts - ClassicWe would like the dialog box to popup as soon as you attempt to connect to \\192.168.211.1 and ask for valid credentials. Any advise on how to do this would be greatly appreciated.