"called name not present", 'net use' redirection?

[mbayaq]

My question is as follows: Is it possible to access a remote Windows
share from a Win98 or MS-DOS 6.22 client using an alias which is NOT
the target host's actual hostname? I've added an entry to the local
LMHOSTS file which does get me to the point of opening a socket and
attempting communication. However, I then get a "called name not
present" from the server.


Does anyone have ideas or suggestions? Is there some special way I can
construct the "net use" command to get around this? Or perhaps a
server setting (Windows 2003) which will tell it to respond to the
alias I've created?


Here is a very brief network capture from Ethereal:


--


No. Time Source Destination
Protocol Info
12 5.746180 192.168.65.101 192.168.65.1 TCP
38700 > netbios-ssn [SYN] Seq=0 Ack=0 Win=1450 Len=0 MSS=1450
13 5.746211 192.168.65.1 192.168.65.101 TCP
netbios-ssn > 38700 [SYN, ACK] Seq=0 Ack=1 Win=17640 Len=0 MSS=1260
14 5.750980 192.168.65.101 192.168.65.1 TCP
38700 > netbios-ssn [ACK] Seq=1 Ack=1 Win=1450 Len=0
16 5.753518 192.168.65.101 192.168.65.1 NBSS
Session request, to R51-VMNET<20> from INSTALL-10161<00>
17 5.753576 192.168.65.1 192.168.65.101 NBSS
Negative session response, Called name not present
18 5.755810 192.168.65.101 192.168.65.1 TCP
38700 > netbios-ssn [ACK] Seq=73 Ack=7 Win=1445 Len=0

--


I've weeded out domain browser announcements, etc., and have shown only
the connection and session setup attempt from the Win98 box. It does
not need nameservice, as its local LMHOSTS file has the IP. So, it
opens a socket and requests a session, but the server returns a
negative response because "Called name not present".


And spoofing it in WINS did not fix it either. Any other ideas?


Thanks for you help.

 

[Guest]

I think anything is possible, however I don't think anyone has published a
method for doing what you want successfully yet. Every attempt I've ever
read regarding this issue has met with failure. If it could be done I would
assume you'd need to write some kind of NetBIOS mapper that ran on the server
and translated requests for the alias (something similar to port forwarding
in concept, except in this case name forwarding).

Why do you want to ALIAS the NetBIOS name? Maybe there is another way to to
get you the end result you're looking for.

Nick

 

[mbayaq]

I have Win98 boxes that have registry entries and such for programs
that look to a specific server, and that server is being replaced by a
new server with a different name. So I have to find a way to make them
look at the new server without going in and changing hundreds of
entries of the old name.

 

[Guest]

Is a log on script out of the question? If you know the reg keys that
specify the remote NetBIOS name it shouldn't be a problem to have your logon
script make the changes for you (even in 98 I think). Is that something you
could do?

Nick Staff

 

[mbayaq]

I don't actually know where they all are, and I think there are more
than just registry entries too, there are also programs that look for
files on the older server that is being replaced with the newer one.
Thanks for the suggestion though. Any other possible ideas? I will
see in the meantime if I can think of any way to find the old entries.

 

[mbayaq]

That seems like a very good idea for programs, but do you have any
ideas about how I could get the 'net use' command to work? It is
currently used in logon scripts in many of the boxes to access shared
drives. Everything I've tried so far to get net use working has
failed. Thanks.

 

[Guest]

Unfortunately I don't think it can be made to work without an additional
program. If it can be done without additional coding I don't know the way
and I've never come across anyone who does. If you keep looking and find out
how to do it please let me know, but my advice would be to start thinking of
other ways to deal with your situation.

Good luck and if you need help rewriting any log on scripts or modifying
registry entries or config files let me know and I'll be happy to help.

Nick Staff