Question Locked

Cant access shares over router to router VPN

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Got an odd problem, I have a SBS 2003 r2 DC setup at main office, with a router to router VPN setup over two netgear routers. small network on the remote office, using a shared drive for local data.

All 4 remote computers were connected to the domain before being moved to the remote office. 3 are XP Pro sp2, 1 is wk2 sp4.

I can ping the server with no problem from all 4 machines, and they connect to exchange (most of the time)I cannot re connect to the existing shared drives, OR connect to a new server share, and have tried \\192.168.20.**\share as well as \\myserver\share.

The 4 machines use fixed IP in the range of 192.168.2.1 - 4 DNS and Wins are set to the server IP.

Now, I also want to connect a drive map from the server back to the share, I can ping the share machine, but whenever I try to map a drive I get a 'network path not found' message or general 'unable to connect' messages. Despite these messages, I can still connect RVNC both ways as well as exchange when it wants to. I have the server name and IP in hosts file.

I have opened up the share to full access to everyone, (to try and get it working) and the domain users have access to the drives I want to connect to.

Now, I did have this working fine at our old remote office, using the same setup. The only difference is that the remote computer is a new dell. (Both new and old had XP Pro SP2)

It almost seems that only some traffic is being allowed over the network, but I cant see what is wrong! The shared machine has its windows firewall enabled, but file sharing is allowed, and ports 137-9 UNC are open. The other remote machines can access the share OK. They also cannot access the server shares.

Any suggestions as to where to look ?

Regards

Paul

12 replies

by cg it

1 NIC or 2 on the SBS box? RRAS enabled?

by paul cheeseman

To answer BWilmot aswell as CG IT,

1 NIC in the server, using netgear router as gateway. VPN's are connected via this router, using other netgear routers to connect router - router VPN. All machines respond to ping, and exchange traffic, although not great, does work, but thats it.

I have been using FVG318 as main, with dg834g's as end points. All with latest firmware, and configured correctly according to netgear.

It does seem to be the domain unable to cross the vpn. I did at one point, forward all available ports to the server, but this didnt make any difference.

I have RRAS enabled aswell, but thats usually only needed by me, and then only occasionally. Port forwarding is used for the necessary ports to the server.

by mark ovk

Make sure your clients have a different IP range in the new location.

For instance, if the server is (and the workstations were) 192.168.1.x, it should be 192.168.2.x or something.
If it is the same, it will try to connect to the local network (which has a higher priority than the vpn) and will never even reach your server thru vpn.

To be sure what the problem is, you need to give out more data about how you configured the whole network/vpn etc.

Cheers,

Mark

by ic-it

Because you stated the 4 machines have a scope of 192.168.2.1 through 2.4 This is unusual in that normally the port or router gateway would be set to 192.168.2.1 and not the subnet of 192.168.2.0 which defines the network.
Once it has the gateway the router will know the route to the gateway to the
192.168.20.** network.

by paul cheeseman

This problem gets stranger!

It is still only share access that wont work... DNS, WINS, Exchange, IP Printing alll seem to work fine, but not shares!

However .... I connected another point to point VPN in from a second site, but did NOT connect it to the domain, and I can access all the shares perfectly! not a single share cannot be accessed this way. Thats just silly, and seems to point away from it being a local port problem on the server.

I am almost tempted to take all the remote machines off the domain, which to seems a backward step, in order to make a simple task work. I will look at services that we do use and see if I will loose anything useful.

Any other suggestions before I do this ?

Regards

Paul

by paul cheeseman

Sorry, I didnt exactly expain the IP setup very well did I :(

Main Office range is 192.168.20.x
Router/gateway is 192.168.20.99

Sub Office range is 192.168.2.1 - 4
Router/gateway is 192.168.2.99

The Sub office machines originally had their DNS set to the main office DNS server at 20.45, this is now set to the 2.99 router address for reliability until issue is sorted. WINS points at 20.45 too.

I have tried several different combinations recently, none of which work, so basically kept it to the way I think it SHOULD be setup

by thevirtualone

really small network with traffic issues can often time be fixed quickly by adding the netbios protocol.

this will get your users online asap, and give you more time to troubleshoot the real issues.

by paul cheeseman

Added it to the workstations, and I can now map to from the 2.x side to shares on 20.45 which is a good start, but still cant map back from 20.45 (main server) to the shared drive on 2.4 which is the local shared drive on the remote office.

I did notice that the sever version is 'NWLink NetBios and NWLink IPX/SPX/Netbios Compatable' not sure if that will match?

I can now ping longfield3 which correctly shows as 192.168.2.4, but still cant access shares, so its getting there slowly!

Oddly, I can map back to the share on 2.1 which is the W2K machine now, just not the XP ones.

by cg it

you might want to consider disabling RRAS and finding some other sort of Remote Access Solution.

If RRAS is enabled and the listener is on the server's only NIC, then a lot of your traffic is going to be seen as remote access traffic on that NIC.

It might not do anything to solve your problem if you disable RRAS.

on the site to site persistant VPN tunnel, clients [doesn't matter if it's servers or workstations] simply access the tunnel and pass data. like any "workgroup" setup, unless both sides are on the same subnet data can't be passed because the application used to pass data doesn't negotiate a connection and negotiate how data is transfered.

So the endpoints one or both have to relay traffic using a local LAN address. If not then clients are on different subnets.

Netbios is machine name mapped to address so there's some lookup available. you could create a hosts file.

IPX? your not using TCP/IP?

That's about all I can think of. A parting thought would be to try accessing a share over the tunnel with the client IP addressing the same as the other sides subnet. see if that works. or find a way to relay so that the client trying to access the share appears to be on the same subnet. The other thing is that since this is a domain network, remote clients have to be domain clients. If not, SBS will see them as remote clients and RRAS rules apply.

This discussion is closed to new replies.