Archived from groups: microsoft.public.win2000.general (More info?)
My question, then, 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".
Thanks.
My question, then, 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".
Thanks.
Facebook
Twitter
Instagram