Last night I upgraded my FC5 to samba-3.0.23c from 3.0.21b. As a result I can no longer browse shares on the samba server via \\hostname\share\. I can, however, access everything as usual via \\10.0.0.2\share\. Nothing else in my config has changed. The hostname resolves from all machines on the domain correctly so it's doesn't appear to be a name resolution issue. I can see the root shares on the samba server, but when I try to browse them I get the error: "\\hostname\share refers to a location that is unavailable. It could be on a hard drive..." I reverted back to 3.0.21b and the error persists. All clients are having the same identical problem. TIA. -Scott
On 12/7/06, Scott <samba@troutpocket.org> wrote:> Last night I upgraded my FC5 to samba-3.0.23c from 3.0.21b. As a result I can > no longer browse shares on the samba server via \\hostname\share\. I can, > however, access everything as usual via \\10.0.0.2\share\. > > Nothing else in my config has changed. The hostname resolves from all machines > on the domain correctly so it's doesn't appear to be a name resolution issue. I > can see the root shares on the samba server, but when I try to browse them I get > the error: > > "\\hostname\share refers to a location that is unavailable. It could be on a > hard drive..." > > I reverted back to 3.0.21b and the error persists. All clients are having the > same identical problem. TIA. >Is nmbd running on the server? John
Latrell Wang 王獻綱
2006-Dec-08 02:23 UTC
[Samba] Can connect to shares via IP but not hostname
I've ever encountered the same problem but in domain mode. My domain is win2k3 SBS, after sp1, the anonymous access will be closed. At this time, using hostname can't map the network drive, but IP can. I open the anonymous on domain side, and everything works fine. I also have a post on the mailing list as follows: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Hi all: As far as I know, win2k3 sp1 disable anonymous access by default. It will remove user =A1=A7anonymous logon=A1=A8 from pre-windows 2000 compatible access group. Under such circumstance, smbmount will not success because anonymous access will be blocked. One way to solve the problem is to re-add anonymous logon to pre-windows 2000 compatible access group. However, it seems to be a security hole. Does anyone encounter the same problem? How do you get around the problem? My samba version is 3.0.21c.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 Can someone give me some suggestions? Thanks in advance, Latrell. -----Original Message----- From: samba-bounces+latrell.wang=3Dzyxel.com.tw@lists.samba.org [mailto:samba-bounces+latrell.wang=3Dzyxel.com.tw@lists.samba.org] On Behalf Of Scott Sent: Friday, December 08, 2006 2:11 AM To: John Drescher Cc: samba@lists.samba.org Subject: Re: [Samba] Can connect to shares via IP but not hostname John Drescher wrote:> On 12/7/06, Scott <samba@troutpocket.org> wrote: >> Last night I upgraded my FC5 to samba-3.0.23c from 3.0.21b. As a result I >> can no longer browse shares on the samba server via \\hostname\share\. I=20 >> can, however, access everything as usual via \\10.0.0.2\share\. >>=20 >> Nothing else in my config has changed. The hostname resolves from all=20 >> machines on the domain correctly so it's doesn't appear to be a name >> resolution issue. I can see the root shares on the samba server, but when >> I try to browse them I get the error: >>=20 >> "\\hostname\share refers to a location that is unavailable. It could be on >> a hard drive..." >>=20 >> I reverted back to 3.0.21b and the error persists. All clients are having >> the same identical problem. TIA. >>=20 > Is nmbd running on the server?Yes. There are no unusual errors in smbd.log or nmbd.log, either. I can see=20 all the network shares, including those on the samba server, via smbtree. -Scott --=20 To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Chris Smith wrote:> On Friday 08 December 2006 11:59, Scott wrote: >> This is a samba box acting as a DC. > > See the section "Procedure 3.5. Server Validation Steps" in > http://us1.samba.org/samba/docs/man/Samba-Guide/secure.html.Passed all the steps 100%. I can connect via smbclient to //starfish/share from within a local ssh session on starfish *and* via smbclient from another linux box on the network. I still cannot open any shared folders from any windows clients via \\starfish\share, only \\10.0.0.2\share. I have verified that name resolution is working correctly. This one has me baffled. I appreciate all the help. -Scott
On Friday 08 December 2006 18:39, Scott wrote:> I have verified that name > resolution is working correctly.From your Windows clients?
On Wednesday 13 December 2006 12:28, Scott wrote:> Yes.Difficult to believe as lack of NetBIOS name resolution appears to be the culprit. Check these items on your Windows systems: NetBIOS is enabled. WINS server addresses are configured (either manually or by DHCP) and point to your WINS server. Firewall is off (at least during troubleshooting). Make sure that your local hosts and lmhosts files are empty (except for the loopback info in the hosts file), so they are not overriding DNS and WINS lookup. Check this on your Samba PDC: That it is configured to be a WINS server (wins support = Yes). That your wins.dat file has the proper information. If not, stop Samba and delete the wins.dat and wins.tdb files and restart. Also check you nmbd log for info such as: "Samba server MYSERVER is now a domain master browser for workgroup MYDOMAIN on subnet ..." "Samba name server MYSERVER is now a local master browser for workgroup MYDOMAIN on subnet..." Chris
Chris Smith wrote:> That it is configured to be a WINS server (wins support = Yes).This was it. Thanks for suggesting it. -Scott