Hello James, Friday, January 18, 2002, 5:21:45 AM, you wrote:
JP> I'm having a problem with Samba that I can't figure out. I have it JP> installed and I can see the server in Network Neighborhood. When I try to JP> browse to it I get the following error: JP> "\\Piglet is not accessible. JP> The network path was not found." JP> When I try to map to \\piglet\pigletroot I get: JP> The mapped network drive could not be created because the following error JP> has occurred: JP> No service is operating at the destination network endpoint on the remote JP> system. JP> I took the smb.conf from another one of my linux machine that is working JP> and modified it for this one. Changed the computer name, share name, and JP> server description. When I look at Network Neighborhood I see the proper JP> description, so I know it sees it. JP> I also have created an smbpasswd with the same username that I use on JP> Windows 2000, and I have a regular account on the machine with the same JP> username. All three have the same passwords. JP> Here's my smb.conf. Any ideas what I'm missing? JP> Thanks, JP> James JP> (I stripped out unused sections and comments to make it shorter) JP> [global] JP> printing = lprng JP> dns proxy = no JP> security = user JP> encrypt passwords = yes JP> workgroup = DEFAULTWG JP> server string = piglet JP> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 JP> netbios name = piglet JP> log file = /var/log/samba/%m.log JP> load printers = yes JP> printcap name = /etc/printcap JP> max log size = 0 JP> preferred master = no JP> [global] JP> # workgroup = NT-Domain-Name or Workgroup-Name JP> workgroup = DEFAULTWG JP> # server string is the equivalent of the NT Description field JP> server string = Piglet Samba Server JP> # This option is important for security. It allows you to restrict JP> # connections to machines which are on your local network. The JP> # following example restricts access to two C class networks and JP> # the "loopback" interface. For more examples of the syntax see JP> # the smb.conf man page JP> hosts allow = 192.168.1. 127. JP> # this tells Samba to use a separate log file for each machine JP> # that connects JP> log file = /var/log/samba/%m.log JP> # Put a capping on the size of the log files (in Kb). JP> max log size = 0 JP> # Security mode. Most people will want user level security. See JP> # security_level.txt for details. JP> security = user JP> # Most people will find that this option gives better performance. JP> # See speed.txt and the manual pages for details JP> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 JP> # Cause this host to announce itself to local subnets here JP> remote announce = 192.168.1.255 JP> # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names JP> # via DNS nslookups. The built-in default for versions 1.9.17 is yes, JP> # this has been changed in version 1.9.18 to no. JP> dns proxy = no JP> #============================ Share Definitions ============================== JP> [install] JP> path = /install JP> comment = Install Directories JP> browseable = yes JP> valid users = james JP> writable = yes JP> write list = james JP> [pigletroot] JP> path = / JP> browseable = yes JP> user = james JP> only user = yes JP> valid users = james JP> write list = james JP> admin users = james JP> _______________________________________________ JP> Redhat-list mailing list JP> [EMAIL PROTECTED] JP> https://listman.redhat.com/mailman/listinfo/redhat-list James, I think there is a bug in the latest samba server. I've been using samba for eons and never had a problem unitl I upgraded to the latest rpm package on the RH errata site for RH7.2. I have been experiencing the same exact problem that you are. One thing I noticed is that I started getting a "that name already being used" message on my windows machine every time I booted the win machine while samba was running. I had to restart samba to clear the windows error, but I still have random "not accessable problems," and have to restart samba. I will probably downgrade back to the previous verion of the RH package until the bug is fixed. -- Best regards, Badger mailto:[EMAIL PROTECTED] _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
