samba - Jan 2001 - using smbclient without netbios names

I am trying to connect to computers running windows9x knowing only the IP
address using smbclient.

on windows computers i can type \\130.15.210.185 in the address bar and
browse the shares of computers that don't show up in my network
neighbourhood (computers on other subnets don't seem to show up, but i can
still use them by typing the IP in)

I am using smbclient like so:
/usr/bin/smbclient "//130.15.210.185/" -U "craig" -L
"130.15.210.185"
session request to 130.15.210.185 failed (Called name not present)
session request to 130 failed (Called name not present)
session request to *SMBSERVER failed (Called name not present)

now the interesting thing is that that command works fine connecting to a
different computer, which is running windows 2000 instead of windows 9x:
/usr/bin/smbclient "//130.15.211.25/" -U "craig" -L
"130.15.211.25"
session request to 130.15.211.25 failed (Called name not present)
session request to 130 failed (Called name not present)
Password: .... (it works)

so it works instead of saying *SMBSERVER failed.

this message
http://lists.samba.org/pipermail/samba-ntdom/2000-October/029319.html
explains that i think:

"When you try to connect via NetBIOS, you present a calling NetBIOS name
and
a  called NetBIOS name. Usually the called NetBIOS name is the name of the
server in things like \\server\share.
W2K probably only supports two things in the called name field: The NetBIOS
name of the server or *SMBSERVER."

this http://lists.samba.org/pipermail/samba/2000-March/021827.html thread
gets the same error message, but apparently for a different reason (he was
running a solaris nbdaemon)

so my question is, how is that i can use windows9x shares from windows by
typing the IP in (but they don't show up in network nieghbourhood, (although
some close by computers do)) but not with smbclient when all I supply is the
ip address (same as with windows...)?

does windows somehow look up the netbios name and supply it? win9x shares
dont seem to like being accessed by jsut their IP and not their netbios
name.

I tried to make this as clear as possible and let you know what I have
learned so far, i hope it's not too long

thanks in advance,
craig

Hello Craig,
    Just Quickly I didnt read all of your email but here is what I think....
Thanks
    Computers not showing across subnets is becuase you probably havent set
branshing across different subnets up in your smb.conf file to display
computers on         different subnet class's or all together different
ranges

    And Windows9x and NT perform much better with IP lookups rather then
NetBEUI the only time netbios can be compared to IP lookups is when you have
a     WINS Server usually running on your Domain Controller or when NetBEUI
names are performed with DNS lookups......

    Also using NetBEUI with out a Domain Controller is very iffy it sort of
decides when it wants to display the other computers on your LAN
    Also it takes its time to resolve NetBEUI Names into IP's when your not
using a WINS... or Caching them

Thanks Jeff Hall
------------------------------------------
NetworkEclipse (02)65844664
Network Admin/Application Programmer
------------------------------------------

----- Original Message -----
From: "Craig" <9jcm3@qlink.queensu.ca>
To: <samba@us5.samba.org>
Sent: Wednesday, January 10, 2001 5:19 PM
Subject: using smbclient without netbios names

>
> I am trying to connect to computers running windows9x knowing only the IP
> address using smbclient.
>
> on windows computers i can type \\130.15.210.185 in the address bar and
> browse the shares of computers that don't show up in my network
> neighbourhood (computers on other subnets don't seem to show up, but i
can
> still use them by typing the IP in)
>
> I am using smbclient like so:
> /usr/bin/smbclient "//130.15.210.185/" -U "craig" -L
"130.15.210.185"
> session request to 130.15.210.185 failed (Called name not present)
> session request to 130 failed (Called name not present)
> session request to *SMBSERVER failed (Called name not present)
>
> now the interesting thing is that that command works fine connecting to a
> different computer, which is running windows 2000 instead of windows 9x:
> /usr/bin/smbclient "//130.15.211.25/" -U "craig" -L
"130.15.211.25"
> session request to 130.15.211.25 failed (Called name not present)
> session request to 130 failed (Called name not present)
> Password: .... (it works)
>
> so it works instead of saying *SMBSERVER failed.
>
> this message
> http://lists.samba.org/pipermail/samba-ntdom/2000-October/029319.html
> explains that i think:
>
> "When you try to connect via NetBIOS, you present a calling NetBIOS
name
and
> a  called NetBIOS name. Usually the called NetBIOS name is the name of the
> server in things like \\server\share.
> W2K probably only supports two things in the called name field: The
NetBIOS
> name of the server or *SMBSERVER."
>
> this http://lists.samba.org/pipermail/samba/2000-March/021827.html thread
> gets the same error message, but apparently for a different reason (he was
> running a solaris nbdaemon)
>
> so my question is, how is that i can use windows9x shares from windows by
> typing the IP in (but they don't show up in network nieghbourhood,
(although
> some close by computers do)) but not with smbclient when all I supply is
the
> ip address (same as with windows...)?
>
> does windows somehow look up the netbios name and supply it? win9x shares
> dont seem to like being accessed by jsut their IP and not their netbios
> name.
>
> I tried to make this as clear as possible and let you know what I have
> learned so far, i hope it's not too long
>
> thanks in advance,
> craig
>
>

i am no expert, but could it possibly be because the two systems are on
different subnets. From what I understood about the smb protocol, it has
problems going between subnets without a wins server....which may only
provide names for requests. sorry if i'm wrong.

-----Original Message-----
From: samba-admin@us5.samba.org [mailto:samba-admin@us5.samba.org]On
Behalf Of Craig
Sent: Wednesday, January 10, 2001 12:20 AM
To: samba@us5.samba.org
Subject: using smbclient without netbios names



I am trying to connect to computers running windows9x knowing only the IP
address using smbclient.

on windows computers i can type \\130.15.210.185 in the address bar and
browse the shares of computers that don't show up in my network
neighbourhood (computers on other subnets don't seem to show up, but i can
still use them by typing the IP in)

I am using smbclient like so:
/usr/bin/smbclient "//130.15.210.185/" -U "craig" -L
"130.15.210.185"
session request to 130.15.210.185 failed (Called name not present)
session request to 130 failed (Called name not present)
session request to *SMBSERVER failed (Called name not present)

now the interesting thing is that that command works fine connecting to a
different computer, which is running windows 2000 instead of windows 9x:
/usr/bin/smbclient "//130.15.211.25/" -U "craig" -L
"130.15.211.25"
session request to 130.15.211.25 failed (Called name not present)
session request to 130 failed (Called name not present)
Password: .... (it works)

so it works instead of saying *SMBSERVER failed.

this message
http://lists.samba.org/pipermail/samba-ntdom/2000-October/029319.html
explains that i think:

"When you try to connect via NetBIOS, you present a calling NetBIOS name
and
a  called NetBIOS name. Usually the called NetBIOS name is the name of the
server in things like \\server\share.
W2K probably only supports two things in the called name field: The NetBIOS
name of the server or *SMBSERVER."

this http://lists.samba.org/pipermail/samba/2000-March/021827.html thread
gets the same error message, but apparently for a different reason (he was
running a solaris nbdaemon)

so my question is, how is that i can use windows9x shares from windows by
typing the IP in (but they don't show up in network nieghbourhood, (although
some close by computers do)) but not with smbclient when all I supply is the
ip address (same as with windows...)?

does windows somehow look up the netbios name and supply it? win9x shares
dont seem to like being accessed by jsut their IP and not their netbios
name.

I tried to make this as clear as possible and let you know what I have
learned so far, i hope it's not too long

thanks in advance,
craig