VPN connect-Ok, but....

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

....sorry for my english..

I try connect to my Local network in office from home (win XP), but i no
see computers!!
Local network
Windows 2000 server, 192.168.1.150 - netcard in local network
192.168.2.200 - netcard to ADSL-mode
Active Directory, DNS, DHCP, WINS, RRAS. Internet over Kerio Winrout
Firewall 5.1.9. Open ports for VPN: PPTP, GR
ADSL modem have static ip-adress from internet-provider

then i connect to LAN, authorisation - ok, but i not see network!!
On RRAS i get tunnel ip-adress 192.168.200.2, server get ip-adres
192.168.200.
ping 192.168.200.1 - o
ping 192.168.1.150 - not response :(((
May be necessary tune RRAS? How i can this

Please HELP!!
 
check the routing table or make sure you have enabled ip routing.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Do you have RRAS enabled as a LAN router? Because your remote client is
not in the same IP subnet as the LAN machines, the RRAS server needs to
route between the two subnets.
 
-------------------------
----- Robert L [MS-MVP] wrote: ----

check the routing table or make sure you have enabled ip routing

--
For more and other information, go to http://www.ChicagoTech.ne
-----------------------

http://www.ChicagoTech.net - very good website!!! Thank you

On my server ip-routing enabled, but i can't tune route between the two subnets, because i first time work with RRAS
Please, help me in my config
 
----- Bill Grant wrote: ----

Do you have RRAS enabled as a LAN router? Because your remote client i
not in the same IP subnet as the LAN machines, the RRAS server needs t
route between the two subnets
 
route print

==========================================================================
0x1 ........................... MS TCP Loopback interfac
0x1000002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interfac
0x1000003 ...00 03 47 32 2e f2 ...... Intel(R) 82540EM Based Network Connectio
0x11000004 ...00 03 47 32 2e f1 ...... Intel(R) PRO Adapte
==========================================================================
==========================================================================
net adress mask gateway interface metri
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.200
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
192.168.1.0 255.255.255.0 192.168.1.150 192.168.1.150
192.168.1.150 255.255.255.255 127.0.0.1 127.0.0.1
192.168.1.255 255.255.255.255 192.168.1.150 192.168.1.150
192.168.2.0 255.255.255.0 192.168.2.200 192.168.2.200
192.168.2.200 255.255.255.255 127.0.0.1 127.0.0.1
192.168.2.255 255.255.255.255 192.168.2.200 192.168.2.200
192.168.200.1 255.255.255.255 127.0.0.1 127.0.0.1
224.0.0.0 224.0.0.0 192.168.1.150 192.168.1.150
224.0.0.0 224.0.0.0 192.168.2.200 192.168.2.200
255.255.255.255 255.255.255.255 192.168.1.150 192.168.1.150
GW: 192.168.2.
==========================================================================
 
You should not need to add any routes. Just check that routing is
enabled. RRAS will route automatically between its interfaces.

What is the default route of your LAN clients? Is it the RRAS router?
eg

Internet
|
router
192.168.2.1
|
192.168.2.200 dg 192.168.2.200
RRAS ----------------------------------VPN
192.168.1.150 dg blank
|
LAN clients
192.168.1.x dg 192.168.1.150

If LAN routing is enabled in RRAS, a remote client using 192.168.200.x
should be able to ping any 192.168.1.x machine.

PMP said:
route print:

===========================================================================
0x1 ........................... MS TCP Loopback interface
0x1000002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x1000003 ...00 03 47 32 2e f2 ...... Intel(R) 82540EM Based Network Connection
0x11000004 ...00 03 47 32 2e f1 ...... Intel(R) PRO Adapter
===========================================================================
===========================================================================
net adress mask gateway
Click to expand...
interface metric
 
Back
Top