Alex,

Ajay's solution works, but can cause problems in a Win2k domain (esp. when
not using WINS) because it changes the way name lookups are done.

We are working with an FS implemented as a loopback SMB server here. We
originally tried the SmbDeviceEnabled setting, but we had problems with
group policy in our domain. Now, ee use Method 3 under MS KB article
Q265861 ("Behavior Changes in Microsoft Network Services").

http://support.microsoft.com/support/kb/articles/Q265/8/61.asp

In particular, we install the MS loopback adapter, set its IP & netmask
(just so it won't conflict with any autoconfigured adapters), and rename the
connection from the default "Local Area Connection <N>" to some name we use.

Our server then finds the adapter by connection name and figures out the
LANA to bind to based on that. The server also gets the IP address for the
adapter and writes it into the hosts file with whatever names we want to use
to get at the server from that machine.

One neat feature is that the FS can be reached via the same name on all
machines (e.g., \\FOOFS\...) because we just write the name into each
machine's host file. The name we register using NetBIOS is anything.
(We're actually going to do unique name registration based on the MAC
addresses of the primary adapter, but for now we do machinename with extra
stuff at the end.)

[BTW, does anyone know what happens today on a Windows network if you have
long machine names of the form REALLYLONGMACHINENAME-{1,2,3,etc}? How does
the name registration deal with that? Or are Windows machine names
restricted to fewer than 16 characters?]

If you'd like, I could track down all the relevant code and post it. (Just
be warned that it might take a little bit of time to track all that down,
esp. the connection name to LANA code, since I did not work directly on
that.)

- Danilo

Ajay Agrawal [aajayIN.IBM.COM] wrote:

> HI Alex,
>
> It is possible to run multiple cifs/smb servers on W2K, but yo have to
> enable it by making the following enrty in the registry
>
> HLM/system/currentcontrolset/services/netbt/parameters
>
> DWORD SMBDeviceEnabled = 0
>
> Thanks
> -Ajay

Alex Ludman [aludmanESCHERGROUP.COM] wrote:

> I have a CIFS Server implementation that runs well on Windows NT 4. It
> has no problem running on Windows 2000 but if I try to connect to it
> locally using "net use * \\mymachine$\myshare" or from explorer the
> server does not even get a connection notification. The error reported
> by the client is "The network name cannot be found." (Error: 67)
> If I shut down the server service everything works fine.
>
> Clients are able to connect from remote machines whether they are NT 4 or
> Win2K.
>
> The server registers a NetBIOS name which is the name of the machine
> suffixed with "$" (so it will not conflict with the server services
> NetBIOS name).
>
> Is it possible to run (and connect to) multiple CIFS servers
> simultaneously
> on a Win2K machine?
> Is there an alternative way to provide a file system interface (without
> having to write a file system driver)?
> Is there a way to create a new File Service in Active Directory
> for my CIFS
> Server and specify an alternative TCP port (alternative to port 445) for
> accessing it?
> Is there a way to connect from a Win2K client to a CIFS server that is
> listening on a port other 445?
>
> I would be glad to hear any suggestions.
>
> Thanks,
> Alex

----------------------------------------------------------------
Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
contains important info including how to unsubscribe. Save time, search
the archives at http://discuss.microsoft.com/archives/index.html

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]