SMB mapping 127.0.0.1 to remote

[Martin.Sheppard at csiro.au]

Hi,

I can map a drive on Win98 to an IP address. I don't think there is anything
special about my setup. One thing to be wary of is that sometimes a windows
smb server can be picky about what you call it. I'm not sure exactly when
the problem arrises, but you can't always say make a static entry in a wins
server for a different netbios name to the one actually used and have it
work.

Hope this helps,

Martin.

-----Original Message-----
From: David Lechnyr [mailto:david at hr.uoregon.edu] 
Sent: Thursday, 18 October 2001 8:58 AM
To: samba-technical at lists.samba.org
Subject: SMB mapping 127.0.0.1 to remote

I need the advice of someone who understands the protocol differences
between Win9x and Win2k to help me solve an ongoing problem.  What I've
determined is that if you map a drive on a Win2k box to \\127.0.0.1\myshare
it works flawlessly using SSH tunneling; however on a Win9x box the mapped
drive works only in DOS windows, and freezes in under a minute (i.e., until
then it is fully functional) under the GUI.

My theory (and where I need the insight/help) is this:  Under Win9x, there
does not appear to be a way to map a drive letter to an IP address; you have
to use lmhosts entry.  However, under Win2k, you _can_ map to an ip address
without using lmhosts, and it works flawlessly.  Given Microsoft's (ahem)
poor history with code re-use, is it possible that this is not a result of a
re-designed GUI, but rather somewhere in the packet headers, the mapped name
is stored and results in an error if it's not an IP?  I've attempted to use
the same "localhost   127.0.0.1" entry on both server and client lmhosts
(with #PRE on the Win9x box), but each and every time it fails.

Upgrading to Win2k just doesn't appeal to me as a solution; can anyone offer
any insight into the behaviors I've described?

Thanks,
David Lechnyr