VPN HELP :)

[Trevah]

My friend and I both have xp pro....I setup a vpn "server".......he setup a vpn "client"......he can connect to my computer but he cannot view the contents of my shared folders or a mapped drive......we are both on AT&T "Dynamic" Broadband and using PTPP. Any help would be greatly appreciated.....Paypal maybe

 

[dmcowen674]

Originally posted by: Trevah
My friend and I both have xp pro....I setup a vpn "server".......he setup a vpn "client"......he can connect to my computer but he cannot view the contents of my shared folders or a mapped drive......we are both on AT&T "Dynamic" Broadband and using PTPP. Any help would be greatly appreciated.....Paypal maybe

If he can connect then it is just the permissions you have to set on your side as the server to allow the client to see what you have shared. If you are in fact connected then you get a "Getting Configuration" message from the client side upon a succesful login. Then it is a matter of what you have set on the server allowed to be open to any clients.

 

[Trevah]

Is there anyway you could help me to find what settings I need to set or change? In the tcpip settings of the incoming properties I have it set to allow callers to access my local area network...to assign ip automatically via dhcp...... in the nwlink I have it set to allow callers to access my local area network.....in the client for microsoft networks i have the rpc set to windows locater....and when I look at specific properties of a user I can only change password and allow callback......thanks for responding.....

 

[dmcowen674]

OK, the intersting thing here is that you have established that to have a valid connection right? You can see his machine and he sees yours but you can't go anywhere on the systems with the connection?

If that is the case sometimes there is some MTU/RWIN settings that set the packets too large to get through the "narrowed" VPN link. A VPN link is an "encapsulated" link, literally a tunnel instead of an open bridge so the packets can't be the same size. For example it's like trying to drive a 13 ft tractor trailer through a 11 ft high tunnel. You have to go through with a smaller rig.

I just realized something, is the ATT (Comcast) cable or DSL? Most cable installs cannot handle VPN protocols (because of the above, you get speed but not enough overhead to add VPN or other Protocols), another reason DSL is superior.

 

[Trevah]

Originally posted by: dmcowen674
OK, the intersting thing here is that you have established that to have a valid connection right? You can see his machine and he sees yours but you can't go anywhere on the systems with the connection?

If that is the case sometimes there is some MTU/RWIN settings that set the packets too large to get through the "narrowed" VPN link. A VPN link is an "encapsulated" link, literally a tunnel instead of an open bridge so the packets can't be the same size. For example it's like trying to drive a 13 ft tractor trailer through a 11 ft high tunnel. You have to go through with a smaller rig.

I just realized something, is the ATT (Comcast) cable or DSL? Most cable installs cannot handle VPN protocols (because of the above, you get speed but not enough overhead to add VPN or other Protocols), another reason DSL is superior.

That does not make much sense. How would a VPN be possible via a 56k dialup and not Cable. Currently AT&T up is 256kbps and Down is 1.7Mbps. I understand what you mean when you talk about packet size but I still think it must be some type of setting just isn't setup right.... Thanks for your help.

 

[bobcpg]

start > run > \\<his ip address>

after your connected

 

[dmcowen674]

Originally posted by: Trevah

Originally posted by: dmcowen674
OK, the intersting thing here is that you have established that to have a valid connection right? You can see his machine and he sees yours but you can't go anywhere on the systems with the connection?

If that is the case sometimes there is some MTU/RWIN settings that set the packets too large to get through the "narrowed" VPN link. A VPN link is an "encapsulated" link, literally a tunnel instead of an open bridge so the packets can't be the same size. For example it's like trying to drive a 13 ft tractor trailer through a 11 ft high tunnel. You have to go through with a smaller rig.

I just realized something, is the ATT (Comcast) cable or DSL? Most cable installs cannot handle VPN protocols (because of the above, you get speed but not enough overhead to add VPN or other Protocols), another reason DSL is superior.

That does not make much sense. How would a VPN be possible via a 56k dialup and not Cable. Currently AT&T up is 256kbps and Down is 1.7Mbps. I understand what you mean when you talk about packet size but I still think it must be some type of setting just isn't setup right.... Thanks for your help.

I'll be out all day today so I'll get back to this tomorrow. There is some settings that if they are not set for the High Speed will not allow VPN to work properly even if you have 1.7 Meg bandwidth available.

Check out the FAQ's for VPN clients such as Cisco, Sonicwall and Contivity, they will clue you in.

 

[Trevah]

dmcowen - thanks for your help thus far.....My friend and I have been checking things out and I think it might have something to do with the rwin settings....anyhow further help from you would greatly be appreciated....thanks again

 

[dmcowen674]

Originally posted by: Trevah
dmcowen - thanks for your help thus far.....My friend and I have been checking things out and I think it might have something to do with the rwin settings....anyhow further help from you would greatly be appreciated....thanks again

Exactly, those settings may be stripping down the packets too much to allow the VPN over High Sped to work.
Use the DRTCP utility at DSLReports.com