Help ! can't see machines inside network thru VPN 1

[boardburner]

I need a serious network guru.........
I have been going thru a bunch of postings on different forums and newsgroups with my problem and no one seems to have a handle on what is happening.

Client: xp pro, thru linksys router, over broadband.
Win sbs2000: server @ work, thru same type router, on DSL.
I "CAN" establish a VPN connection with the server.
I "CAN" establish an RDT session with the server.

I "CAN'T" see or establish a session of any kind with any machines on the internal network. I "CAN'T" ping thru the VPN any machines inside the network. I am not even sure how I am getting an RDT session with the server when I can't get thru to the network?

Need direction
Thanks

 

[ChicagoTechNet]

assuming you have two NICs, have you enabled IP routing?

For more tips or information, go to

http://www.ChicagoTech.net

>VPN

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network and How to at

http://www.ChicagoTech.net

 

[attrofy]

I am giving you a star for a very helpful link - lots of good resources and info at your fingertips on that site.

Thank you

 

[ChicagoTechNet]

Thank you.

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network and How to at

http://www.ChicagoTech.net

 

[boardburner]

I personnaly didn't set this system up....just trying to figure it out. I know all stations on all loops can access the internet with a permission set.
All internal workstations are running XP Pro.
Home workstations are XP Pro also.
All workstations "will" RDT within the loop 10.0.1.xx of dedicated IP's and all I care about are these ones for outside RDT.

But I am sure that the VPN server IP is 192.168.7.100 and the client is 192.168.7.xxx (variable) on connection.

Loopback = 127.0.0.1
Internal = 192.168.7.100

(3) NIC's in this machine:
1 to the router..192.168.7.2
1 to 10.0.1.xx = Dedicated IP's
1 to 10.0.0.xx = DHCP

If this is a enough to help me....let me know. If not let me know what else you need. I am thinking that I have a routing issue here but not sure how to fix.

Thanks
Gene

 

[John Lewis]

Yep, you have routing issues. I am not sure I understand how your server side network is configured, I find I am a bit confused. I will attempt to point you in the right direction.

First, your RDT connection to the server works because the Windows VPN client almost always handles the routing to the VPN server without problem. Routing to the server side network is another issue.

When the VPN is established, information about your server side network is not passed to the VPN client. In order to route properly, the client tries to guess the network addressing scheme based upon the VPN address. If the client gets a class C address as specified in RFC1918 (as looks like in your case), a route is added to that class c with a class C netmask (255.255.255.0). If you do a 'route print' on the client with the tunnel up, I'm sure you will see this.

I could speculate a bit more, but would be better to get the facts straight. You mentioned a 192.168.7 network, I would assume you are using a /24 (255.255.255.0) mask, but you didn't say. You also mention 10.0.0 and 10.0.1 -- you didn't give a mask. If you are using a /24 here, these would be two separate networks. If you are using a /8, they would simply be different ranges on the same network. Which is the case? Do you need to access the 192.168.7 network and the 10.0 network(s), or just one or a combination of two?

 

[boardburner]

FIXED.!!
It appears that by forcing the workstations on the static loop to use the server 10.0.x.xx IP on that sub as the default gateway, all is fixed.! RDT over the VPN working like a bear.

I want to thank all who tried different solutions.

Gene