Tunnelling Samba via ssh might need gateway metric set - SMB

This is a discussion on Tunnelling Samba via ssh might need gateway metric set - SMB ; If you are tunnelling Samba via ssh using the Microsoft Loopback Adapter on Windows 2000, you may have to disable and re-enable the Microsoft Loopback Adapter to get your Internet connection and tunnelling working at the same time. If your ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Tunnelling Samba via ssh might need gateway metric set

  1. Tunnelling Samba via ssh might need gateway metric set

    If you are tunnelling Samba via ssh using the Microsoft Loopback
    Adapter on Windows 2000, you may have to disable and re-enable the
    Microsoft Loopback Adapter to get your Internet connection and
    tunnelling working at the same time. If your Internet connection
    doesn't work in this case, use "route print" at the Command Prompt and
    compare the active routes. The list of routes may be different.

    To fix it, go to Start|Settings|Network and Dial-Up Connections and
    double-click on the Microsoft Loopback Adapter. Go to Properties, then
    click on Internet Protocol (TCP/IP), then Properties, then Advanced...
    and click on the item in the Default gateways: list control. Then,
    press Edit and change the Metric from 1 to 2. It should now be fixed.

    If you do "route print" again, you'll see one of the entries has a 2 in
    its Metric column. A lower metric is actually higher priority; a
    higher metric tells Windows to use other routes first. By changing the
    metric from 1 to 2, you are telling Windows to try other routes first,
    that is, use the route to the gateway on your real network adapter
    rather than on the Microsoft Loopback Adapter (even if the route from
    the Microsoft Loopback Adapter is at the beginning of the list of
    routes). By disabling and re-enabling, you actually cause Microsoft
    Loopback Adapter routes to appear further down in the list so that's
    why that fiddling worked before.


  2. Re: Tunnelling Samba via ssh might need gateway metric set

    You might use Putty to tunnel Samba via ssh.

    Daniel Howard wrote:
    > If you are tunnelling Samba via ssh using the Microsoft Loopback
    > Adapter on Windows 2000, you may have to disable and re-enable the
    > Microsoft Loopback Adapter to get your Internet connection and
    > tunnelling working at the same time. If your Internet connection
    > doesn't work in this case, use "route print" at the Command Prompt
    > and compare the active routes. The list of routes may be different.
    >
    > To fix it, go to Start|Settings|Network and Dial-Up Connections and
    > double-click on the Microsoft Loopback Adapter. Go to Properties,
    > then click on Internet Protocol (TCP/IP), then Properties, then
    > Advanced... and click on the item in the Default gateways: list
    > control. Then, press Edit and change the Metric from 1 to 2. It
    > should now be fixed.
    >
    > If you do "route print" again, you'll see one of the entries has a 2
    > in its Metric column. A lower metric is actually higher priority; a
    > higher metric tells Windows to use other routes first. By changing
    > the metric from 1 to 2, you are telling Windows to try other routes
    > first, that is, use the route to the gateway on your real network
    > adapter rather than on the Microsoft Loopback Adapter (even if the
    > route from the Microsoft Loopback Adapter is at the beginning of the
    > list of routes). By disabling and re-enabling, you actually cause
    > Microsoft Loopback Adapter routes to appear further down in the list
    > so that's why that fiddling worked before.



+ Reply to Thread