<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: <cipe-l,AT,inka,DOT,de>
Subject: Win2k through Router
From: "David A. Osborn" <david.osborn,AT,mchsi,DOT,com>
Date: Wed, 1 Oct 2003 16:42:22 -0500

I am currently working on setting up a Win2K box (192.168.10.1) with a VPN connection to a Linux box(192.168.1.248) I am using as a router.  The goal is to allow the Win2K box to be able to share printers and files as if it was on the network on the other side of the router (the network on the other side of the Linux box being 192.168.1.0)
 
I can ping just fine from the Win2k box to the Linux box over the VPN as well as from the Linux box to the Win2K.  Here's a windump of that
 
01:11:07.848992 arp who-has 192.168.1.248 tell alhome
01:11:07.849217 arp reply 192.168.1.248 is-at 8:0:58:0:0:2
01:11:07.849227 IP alhome > 192.168.1.248: icmp 40: echo request seq 15616
01:11:07.952068 IP 192.168.1.248 > alhome: icmp 40: echo reply seq 15616
01:11:08.659241 IP alhome.137 > 192.168.1.248.137: udp 50
01:11:08.659501 IP alhome.137 > 192.168.1.248.137: udp 50
01:11:08.765117 IP 192.168.1.248 > alhome: icmp 86: 192.168.1.248 udp port 137 unreachable
01:11:08.848344 IP alhome > 192.168.1.248: icmp 40: echo request seq 15872
01:11:08.952102 IP 192.168.1.248 > alhome: icmp 40: echo reply seq 15872
01:11:09.848316 IP alhome > 192.168.1.248: icmp 40: echo request seq 16128
01:11:09.952631 IP 192.168.1.248 > alhome: icmp 40: echo reply seq 16128
01:11:10.145106 IP alhome.137 > 192.168.1.248.137: udp 50
01:11:10.145151 IP alhome.137 > 192.168.1.248.137: udp 50
01:11:10.249261 IP 192.168.1.248 > alhome: icmp 86: 192.168.1.248 udp port 137 unreachable
01:11:10.848252 IP alhome > 192.168.1.248: icmp 40: echo request seq 16384
01:11:10.947951 IP 192.168.1.248 > alhome: icmp 40: echo reply seq 16384
01:11:11.644977 IP alhome.137 > 192.168.1.248.137: udp 50
01:11:11.645020 IP alhome.137 > 192.168.1.248.137: udp 50
01:11:11.749608 IP 192.168.1.248 > alhome: icmp 86: 192.168.1.248 udp port 137 unreachable
 
If I try to ping something inside the router like 192.168.1.200  from the Win2k box it shows up on a windump of the CIPE connection on the Win2K side, but not on a tcpdump of the CIPE connection on the Linux side.  Any ideas?  Below is the route table on the Win2k system incase it is of any use.  I tried the route table both with and without the static route to 192.168.1.200, but the effects were the same.
 
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...08 00 58 00 00 01 ...... DKW Heavy Industries VPN Adapter.
0x1000004 ...00 0c 76 26 0f 8b ...... VIA Rhine II Fast Ethernet Adapter                         
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask               Gateway           Interface       Metric
          0.0.0.0                  0.0.0.0                  192.168.0.1     192.168.0.4   1
        127.0.0.0                255.0.0.0              127.0.0.1         127.0.0.1       1
      192.168.0.0              255.255.255.0      192.168.0.4     192.168.0.4   1
      192.168.0.4              255.255.255.255  127.0.0.1         127.0.0.1       1
    192.168.0.255            255.255.255.255  192.168.0.4     192.168.0.4   1
      192.168.1.0              255.255.255.0      192.168.10.1   192.168.10.1 1
    192.168.1.200            255.255.255.255  192.168.10.1   192.168.10.1 1
     192.168.10.0             255.255.255.0      192.168.10.1   192.168.10.1 1
     192.168.10.1             255.255.255.255  127.0.0.1         127.0.0.1       1
   192.168.10.255           255.255.255.255  192.168.10.1   192.168.10.1 1
        224.0.0.0                224.0.0.0              192.168.0.4     192.168.0.4   1
        224.0.0.0                224.0.0.0              192.168.10.1   192.168.10.1 1
  255.255.255.255          255.255.255.255  192.168.10.1   192.168.10.1 1
Default Gateway:       192.168.0.1
 
.

<< | Thread Index | >> ]    [ << | Date Index | >> ]