Link to home
Start Free TrialLog in
Avatar of nikdonovanau
nikdonovanau

asked on

VPN No network provider accepted given path PLEASE HELP

Hi Experts

Any help appreciated.

I have 2 win2k3 servers at different locations

I connect server A to server B over internet VPN

Port forward 1723 on linksys router on server B

connects - authenticates - logs in no problem at all

Server B is a DHCP server to incoming connections.

I can use VNC to connect to server B using a lan IP 192.168.1.100

BUT I cannot access any of the network shares on server B

I tried DMZ very quickly and with no luck then turned it off again.

I can VNC backward and forward between both server a and b so I am guessing that the TCP Protocol is getting through ok.

I can ping no problem at all

any ideas??

Thanks very much.
Nik
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Do both networks use the same 192.168.1.x subnet? If the "network shares" are located on other computers/servers ate site B, you will not be able to connect with the subnets being the same.
Avatar of nikdonovanau
nikdonovanau

ASKER

Server A uses 192.168.1.100 and server B uses 192.168.0.1
Will I have to change one of them?
No that is fine, if you are using a subnet mask of 255.255.255.0 at both sites. However, a mask of 255.255.0.0 will cause problems with those IP's.
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for that, When I try to connect to \\192.168.1.100\share I get the error 'no network provider acc...'
Odd error for that problem. Do you get an error number with it such as 67 system error?
I assume that share is available from the local network and has been tested as OK?
The share is actually on the VPN server 192.168.1.100 ? Not on another system and the server has 2 NIC's ? Though that should work, with 2 NIC and other devices (may have to tweak), just try the VPN server for now as a test.
Are there any software firewalls on the server. They can be configured to allow local traffic only.
What kind of hardware firewall is on site B ?
Try mapping a drive, but with user credentials, at a command line enter:
net  use  z:  \\192.168.1.100\ShareName  password  user:/username@domainname.abc
(note "user" is not a variable)
Then try to connect to Z:
Apparently it is possible to get that error if you are logged in with different credentials, though it will usually ask you for them.
Thanks RobWill. Sorry for the delay. I have tried that and got a error 67. firewall setup is:
 Linksys ADSL 2 Router with http & mail ports open and forward to server -> D-Link VPN Router (in Linksys DMZ) forward vpn to server -> server with no software firewall.
The strange thing is I can ping 'server' and it resolves to 192.168.1.100 and I get 0% packet loss.
I can even VNC direct by typing 'server' in the connection box.

Thanks again for you help thus far.
Do I understand correctly you have a D-Link router in series with a Linksys router ? VPN's specifically the GRE protocol does not like multiple NAT (network Address Translation) devices such as 2 routers. Often the basic connection can be made, but completion of the "handshaking" cannot take place, allowing you to access resources.
Perhaps you can elaborate on the hardware and subnets used at Site B.
Thanks for that - the connection logs in very quickly - the D-LINK VPN Router is in the DMZ of the Linksys router and forwards VPN to the server. When I first set the VPN (before the dlink) up I went as far as placing the server in the DMZ and got the same problem. What I might do is try to connect 2 pc's together instead of the 2 servers. It has to be one of the servers not allowing browsing?
Odd, I am stumped.
Only suggest I have is there have been 2 posts lately where users could only connect to some resources via VPN\. Disabling/un-installing RRAS and re-installing in the exact same fashion, repaired the issues. Seems routing may get "messed up" when configured. However in your case you can ping the system to which you want to connect so I am doubtful. Almost sounds like a firewall rule with an exception that allows local file and print access, but not from other networks/subnets.
thanks for all the help guys - PC to PC connection seems to work ok so there is a problem somewhere with the server blocking ports or wins or tcp is messed up somewhere. I think the easiest way from here would be to reinstall.
your solution works fine when connecting direct to the PC - thanks for the workaround

Nik.
Thanks Nik, good luck with it.
--Rob