samba - Jun 2002 - Win98 not doing name resolution.

I recently reinstalled Linux on my fileserver (RedHat 7.2), which was 
running Samba (v 2.2.1a). Now, trying to reconfigure Samba back to its 
original state (silly me didn't keep a copy of the conf file) I've run
into
a problem. My win98 machines can't find the Samba server by name, but they 
can by number. By this I mean:

On a Linux desktop,

smbclient -L //marvin/

works as expected. No problems there. However on a win98 desktop,

ping marvin
nbtstat -A 10.0.0.1
net view \\10.0.0.1

all work as expected, but

nbtstat -a marvin
net view
Network Neighborhood

fail or don't display the server, and

net view \\marvin

and typing \\marvin into Explorer don't work at first, but once I do a

net view \\10.0.0.1

they do. This all seems very odd to me, my guess is that it has something 
to do with NetBIOS name resolution, but I'm not sure and I wouldn't know
how to correct it anyway. Can someone give me a pointer as to what might be 
the problem?

                         Thanks,
                                 Tim Bates

Would just putting your server into lmhosts on the client fix this?

Have you gone through the DIAGNOSIS.txt guide in docs/textdocs section of
your source files?
Joel
> I recently reinstalled Linux on my fileserver (RedHat 7.2), which was 
> running Samba (v 2.2.1a). Now, trying to reconfigure Samba back to its 
> original state (silly me didn't keep a copy of the conf file) I've
run into
> a problem. My win98 machines can't find the Samba server by name, but
they
> can by number. By this I mean:
> 
> On a Linux desktop,
> 
> smbclient -L //marvin/
> 
> works as expected. No problems there. However on a win98 desktop,
> 
> ping marvin
> nbtstat -A 10.0.0.1
> net view \\10.0.0.1
> 
> all work as expected, but
> 
> nbtstat -a marvin
> net view
> Network Neighborhood
> 
> fail or don't display the server, and
> 
> net view \\marvin
> 
> and typing \\marvin into Explorer don't work at first, but once I do a
> 
> net view \\10.0.0.1
> 
> they do. This all seems very odd to me, my guess is that it has something 
> to do with NetBIOS name resolution, but I'm not sure and I wouldn't
know
> how to correct it anyway. Can someone give me a pointer as to what might be
> the problem?
> 
>                          Thanks,
>                                  Tim Bates
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

>Would just putting your server into lmhosts on the client fix this?
I don't have an lmhosts on the client, it's worked before without it,
and
it works from a Linux box without it too. But I'll try it.
...
Now it can be addresses directly without having to go through the step of 
addressing it by IP, but it still doesn't show in Network Neighborhood.
>Have you gone through the DIAGNOSIS.txt guide in docs/textdocs section of
>your source files?
Yes. It all seems to work, bar not showing up in Network Neighborhood. And 
without the lmhosts entry it isn't accessible by name until I've
accessed
it by address, as I described earlier. What puzzles me most is that my 
Linux desktops (including this self same machine when booted in Linux) have 
no problems at all.

                         Thanks,
                                 Tim Bates