[Samba] Windows won't recognize hostname of server

[Don.Walters at FalconJet.com]

> Are you sure you don't have another system going by the Netbios name
of
> MIS001 on your network?  Ask your WINS server to resolve MIS001 for
you
> and see if it returns the correct ip..
> 
> nmblookup -R -U ipaddr.of.wins.server mis001


Ok, now when I run this command, I get...

[root at mis001 root]# nmblookup -R -U ipaddr.of.wins.server mis001
querying mis001 on 0.0.0.0
192.163.11.2 mis001<00>
[root at mis001 root]#


Which is the correct answer.  However, I still cannot access the server
using the hostname.  I have also tried putting my hostname/ip in my
lmhosts file on Windows and it still won't recognize the hostname.

Again, here is my conf file.


[global]
	workgroup = DFJ
	netbios name = mis001
	server string = MIS Catia Support Server
	security = SHARE
	password server = lr-dc01
	encrypt passwords = yes
	log file = /var/log/samba/log.%m
	read raw = No
	name resolve order = wins host bcast
	socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
SO_KEEPALIVE
	load printers = No
	lm announce = Yes
	wins server = 192.161.200.1
	kernel oplocks = No
	ldap ssl = no
	preload = Yes
	guest ok = Yes
	ldap ssl = no


Here's one fruitless command....

C:\Documents and Settings\waltersd>net view \\mis001
System error 5 has occurred.

Access is denied.

C:\Documents and Settings\waltersd>


After another...

C:\Documents and Settings\waltersd>net view \\mis001
System error 5 has occurred.

Access is denied.

C:\Documents and Settings\waltersd>


Someone already suggested I upgrade to the latest Samba and I'd like to
do that, but since this is a production box and users are continually
accessing the shares, I don't want to upset everything by taking down
the system for an update.  If it starts to look like I've exhausted
everything else, I will notify my users and come in over the weekend and
upgrade, but I really feel like this should be fixable without needing
to upgrade Samba.