Re: New: LanMan98 V2 Not connecting

In message <5022be8237spam@xxxxxxxxxxxxxx>
VinceH <spam@xxxxxxxxxxxxxx> wrote:

In article <2070bb2250.GrahameParish@xxxxxxxxxxxxxx>,
Grahame Parish <spamtrap@xxxxxxxxxxxxxxx> wrote:
In message <5022b64dd3chris@xxxxxxxxxxxx>
Chris <chris@xxxxxxxxxxxx> wrote:

[LanMan uses NetBIOS, so needs the NetBIOS name, not the hostname]

Thanks, but where can I find a PC's 'NetBIOS name'? Presumably
it's not the same as the 'computer name' in 'System Properties.

Yes, it is[1]. That's the reason I said to look there in the first
place. :/

[1] For all I know, it might be possible to make the two differ - but
if it is, I doubt the method is something trivial that would be done
by the average user. In all likelihood, therefore, on most (if not
all) Windows machines, the computer name as found in the system
properties is the NetBIOS name.

ie. how does one do '*Show *NetBIOS*' in Windows XP?

SET (with no parameters) will list all environment variables - the
one you want is Machinename.

I think it comes up as computername.

Name resolution is always a tricky issue, and I don't know which of
the three possible methods LanMan98 uses, nor in what order.

Have you tried using the IP adress of the XP machine - that will
bypass name resolution issues, altthough I vaguely remember a
discussion about a year ago of different problems that then surfaced -
essentially Windows was rejecting the connection because it hadn't
been addressed by name. I also seem to remember a solution being
posted.

Background:

TCP/IP as standard (i.e. in Unix land, where it originated) uses DNS
naming, and the hosts file. The hosts method is older, but doesn't
scale to large networks, as it involves keeping the files on all the
computers in sync and up to date. The hosts file is NOT used by the
local machine to find its own address.

DNS (Domain Name System) is a distributed naming service which runs on
servers scattered across the Internet, and has the name-to-address
translation defined in one place, possible backed up on secondary
servers).

On Windows computers there is a third system - NetBios, which is the
system developed as part of NetBEUI. As these rely on broadcasts, they
don't work very well on large networks, and in particular are
difficult to get to work across routers. (The method involves setting
up the LMHosts file, telling the system where to find the master
browser. As the master browser is decided by election among the
machines on the network at any one time, this can get messy.)

There is also a fourth method, WINS (Windows Internet Name Service),
which isn't used much. It's also broadcast based.

Windows wil use all three methods in turn to find an adress when given
a name, so for example "ping myiyonix" will try dns, look in the hosts
file, and look in NetBios. The order of these can be altered, and I
don't know what the default is. It doesn't usually matter.

A small number of RISC OS applications can participate in NetBios
naming. LanMan98 appears to be one, and the smbserver is another. I
don't know about Omniclient or Lanman.

The reason for the confusing names LanMan and Lanman98 is that the
Windows protocol thay are implementing is called LAN Manager, which
uses a low-level message protocol called SMB (Server Message Block).
SMB is usually made into a word as SAMBA, hence the mistaken
references to !smbserver as Samba. If you use Samba on Unix you will
know that it is both client and server, whereas smbserver is server
only.



--
Alan Adams, from Northamptonshire
alan@xxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.

Relevant Pages

  • Re: Fileserver question
    ... >> another box running both 9.0 and Windows. ... >> computers in the same room and connected to a router. ... otherwise you will need to run a DHCP server on one ... > of the machines, preferably the server, or give both machines static ...
    (alt.os.linux.suse)
  • nslookup times out on some WinXP clients
    ... Basically, nslookup times out on some Windows machines, but not on others. ... we currently have a Windows 2000 Server DNS & DHCP Server serving IP ...
    (RedHat)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... thesystemtimeis jumping ahead an additional ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ...
    (microsoft.public.windowsxp.general)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ... All patches applied. ...
    (microsoft.public.windowsxp.general)
  • Re: How do I see users that logged in ?
    ... - I know W98 machines should be migrated, but there are to many hindrances: ... Each subdirectory contains sub-subdirectories like administration, drawings, ... I know you can use the $ to share in windows, ... Can you log on to the server as user X and log on localy as user Y ??? ...
    (microsoft.public.windows.server.general)