<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Charlie: Your screen shot attachment did not come through on this
e-mail. Also, The vpn-help list server may reject attachments...<br>
<br>
Matt: What Charlie is trying to say, is that he can't browse SAMBA
shares. i.e. get directory listings from our main Windows file server.<br>
Stuff like smb://servername/sharename does not resolve<br>
<br>
I think the problem is even deeper though. The VPN tunnel comes up,
but we cannot ping any of the machines on the company side of the
tunnel. I took a quick peek at the setup, and it appears to be a
routing issue to me. For whatever reason, shrew soft is not getting
the "remote network topology" from our Adtran gateway router, this was
true with the released windows version as well. So my ShrewSoft
install directions instruct our employees to manually:<br>
<p style="margin-bottom: 0in;">=========== (quote from the Windows
setup directions)=========== <br>
Un-Check the <b>Obtain the remote
network topology and route policy automatically from the peer gateway</b>
check box, and then click the <b>Add</b> button, and then enter a
static route to the ALI network by setting <b>Entry Type</b> to
<b>Network</b>, <b>Net Address</b> to <b>192.168.168.0</b>, <b>Net
Mask</b> to <b>255.255.255.0</b>, and then press <b>OK</b>. The
final “VPN Routing Policy” is shown below. Click <b>Save</b> to
save this VPN configuration.</p>
===========(end quote)=========== <br>
<br>
Our internal network uses addresses in the 192.168.168.* range. The
Adtran gateway router allocates addresses in the 192.168.167.* range
to VPN clients.<br>
<br>
As far as I can tell, Charlie has ShrewSoft setup correctly, with the
required manual network topology as directed in my directions. We can
successfully start the VPN tunnel, but nothing on the company side is
accessible. Pings to known good equipment in the 192.168.168.* range
time out.<br>
<br>
We used the linux route command, to dump the routing table. I'm no
expert in linux IP routing, but it does not look right to me. There
were no entries in the routing table that would direct packets destined
for the 192.168.168.* network to the 192.168.167.1 TAP0 interface
created by the VPN tunnel. Indeed there were NO lines in the routing
table that referenced the 192.168.168.* network at all. I'm fairly
certain that the incorrect routing table is the source of the problem,
however I do not know how iked and the ip routing stuff interact with
each other, so I could be wrong.<br>
<br>
Matt<br>
<br>
charles morrison wrote:
<blockquote cite="mid:46DD6E23.3030806@ledgible.com" type="cite">Matt,
<br>
<br>
I am able to connect to my company network but am unable to browse it.
I had this working before, under the 64 bit install. Here is a screen
shot of the setup and my route table while connected using the VPN
tunnel.
<br>
<br>
VPN set up screenshot
<br>
<br>
Any ideas as to what I should do?
<br>
<br>
Charlie Morrison
<br>
<br>
</blockquote>
<br>
</body>
</html>