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

8 Apr 2005 6:12 PM

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.

10 Apr 2005 12:51 AM

Nick Staff

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

Show quoteHide quote

"mba***@gmail.com" wrote:

> 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.
>
>

11 Apr 2005 5:35 PM

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.

11 Apr 2005 7:21 PM

Nick Staff

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

Show quoteHide quote

"mba***@gmail.com" wrote:

> 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.
>
>

12 Apr 2005 5:25 PM

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.

14 Apr 2005 12:23 AM

Nick Staff

If it were me here's what I'd do:

- Compile a list of all programs under my scope of management that connect
to the server via it's NetBIOS name - call the list NetBIOS Required.

- Find out which if any of these programs are using the NetBIOS name purely
as a locator and out of those which ones will query DNS when NetBIOS
resolution fails

- Remove from the NetBIOS Required list all programs that meet the the
previous steps conditions and put them on a second list called DNS Sufficient.

- For each remaining program on the NetBIOS Required list find out where it
stores it's settings (registry, .ini files, .xyz files (try opening unknown
configuration files with notepad and if it's text or binary), .dat files,
scripted shortcuts (a la Filemaker Pro, etc, etc).

- After completing the previous step, remove from the NetBIOS Required list
all programs that store the servers NetBIOS name in the registry or any file
that can be read using notepad (and doesn't display symbols like this â˜¼) and
put them on a list called Upgrade Scriptable.

- Any programs left on the NetBIOS required list will have to be addressed
individually (maybe there's an upgrade for it, maybe it's being phased out,
maybe it's non-essential, who knows?).

- Add a CNAME (ALIAS) record to DNS with the old server name as the alias
and have it resolve to the new servers A (HOST) record. This should take
care of your DNS sufficient list.

- Write a logon script that edits the registry and all known text files,
replacing the old server name with the new. This should take care of your
Upgrade Scriptable list.

If you provide me with the location of all config files and send me examples
of each so I can see their format I'll write you the script you need. If you
don't want me to see the config data then replace it with generic stuff but
keep all formatting - only change the alphanumeric characters.

Let me know if this helps (hope it does)

Thanks,

Nick Staff

Show quoteHide quote

"mba***@gmail.com" wrote:

> 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.
>
>