Joe Granto wrote:
> 4. On system B, I installed a loopback NIC, as described on various
> web pages. It uses the settings of 10.0.0.1/255.255.255.0, with the
> gateway of my primary NIC (192.168.1.1). I have disabled EVERYTHING
> except TCP/IP on this NIC (no SMB, not NetBT, etc.). Again, only the
> TCP/IP checkbox is checked for this NIC. This has to be done because
> SSH cannot forward a port if that port is in use,and port 445 is used
> on my 192.168.1.x NIC. Thus, I have to use the 10.0.0.1 NIC for
> forwarding port 445. I have installed KB884020, which addresses
> loopback issues.
>
> 5. On system B, I configured the SMB tunnel in putty like so:
> 10.0.0.1:445 local listening port and 192.168.1.99:445 for the
> destination. Putty connects just fine, but the tunnel does NOT work. I
> cannot access any resources from System B using \\10.0.0.1.
>
> Now, I have installed WireShark on System A and sniffed the wire
> during SMB communication attempts. I see the putty traffic just fine
> as I create the tunel. However, no port 445 traffic seems to be
> getting redirected to System A when I try to access \\10.0.0.1
> resources. No traffic at all, actually. There are no incoming or
> outgoing packets.
>
looks like a routing issue to me. can you ping the 10.0.0.1 address?
if not, you need to adjust your settings.

why add a 10.0.0.1 to an 192.168.x.x system? it would be far easier to
use 192.168.2.x in place of the 10.0.0.1 as you could then use a mask of
255.255.240.0.

by the way, what's the IP for sys-A? by the addresses shown, it looks
like your wired to at lease one router -- please describe the physical
layout

--
try a random act of kindness today -- you just might surprise even
yourself