[Samba] Can only connect to Samba thru IP, not FQDN
Hi! I'm running FreeNAS 0.7RC1 with Samba 3.0.34. It's joined to my windows AD, and I can see all users, and etc. My XP clients don't have any issues connecting using either FQDN or IP, while my vista clients suffer from the problem that if I try to connect to the NAS by entering the following address: \\nas01.domain.com, it keeps asking me for username and password, no matter what combinations I try (DOMAIN\username , usern...@domain, username, etc..). Now if I try to connect to Samba using this address format: \\xxx.xxx.xxx.xxx, it successfully connects, without asking for any username or password (it's correctly using my windows domain logon credentials from the current account). How might I go about fixing this weird issue? Is this a client problem (vista), or is there some configuration on the server (smb.conf?) that I have missed? Huge thanks in advance! -- Maxim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can not connect to share for a particular user.
Hi 2008/7/21 David Kuntadi [EMAIL PROTECTED]: make_connection: connection to public denied due to security descriptor. when it successfully connects I see: aragorn (192.168.0.94) connect to service gregi initially as user gregi (uid=1084, gid=1084) (pid 88931) Well, I solved this problem in the most peculiar manner... I created a user on the samba server sharing the drive (not the PDC), tried to connect: it gave me an error and I had to re-join the domain. Since everything works well... No idea what happened -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can not connect to share for a particular user.
On Thu, Jun 5, 2008 at 11:46 AM, Jean-Yves Avenard [EMAIL PROTECTED] wrote: Hello I currently run a few samba servers one being used as a PDC. Today I added a user to the domain and for some reason I can not get it to connect to any of the shares but home on the file server. % smbclient -U gregi //server3/public Password: Domain=[HYDRIX-MALVERN] OS=[Unix] Server=[Samba 3.0.28] tree connect failed: NT_STATUS_ACCESS_DENIED However I can connect with : $ smbclient -U gregi //server3/gregi Password: Domain=[HYDRIX-MALVERN] OS=[Unix] Server=[Samba 3.0.28] smb: \ In the smb log file, I would see make_connection: connection to public denied due to security descriptor. when it successfully connects I see: aragorn (192.168.0.94) connect to service gregi initially as user gregi (uid=1084, gid=1084) (pid 88931) The share entry in smb.conf is: [public] comment = Public folder path = /data/home/public browseable = Yes writable = Yes force create mode = 0777 force directory mode = 0777 force group = public Try to remove: force group = public in smb.conf and then restart samba (/etc/init.d/samba restart). After that try to access again using gregi username, see wehter or not this help. DK -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can not connect to share for a particular user.
Hello I currently run a few samba servers one being used as a PDC. Today I added a user to the domain and for some reason I can not get it to connect to any of the shares but home on the file server. % smbclient -U gregi //server3/public Password: Domain=[HYDRIX-MALVERN] OS=[Unix] Server=[Samba 3.0.28] tree connect failed: NT_STATUS_ACCESS_DENIED However I can connect with : $ smbclient -U gregi //server3/gregi Password: Domain=[HYDRIX-MALVERN] OS=[Unix] Server=[Samba 3.0.28] smb: \ In the smb log file, I would see make_connection: connection to public denied due to security descriptor. when it successfully connects I see: aragorn (192.168.0.94) connect to service gregi initially as user gregi (uid=1084, gid=1084) (pid 88931) The share entry in smb.conf is: [public] comment = Public folder path = /data/home/public browseable = Yes writable = Yes force create mode = 0777 force directory mode = 0777 force group = public I'm at loss... Why would it connect for one share but not the other. A quick google for connection to public denied due to security descriptor. mentioned some people deleting the .tdb file and restarting samba which I did, to no available. This user has been created the same way as all the other users on the PDC: smbpasswd -a gregi and then I enter the password Any help would be greatly appreciated. it's driving me nuts ! Thanks in advance Jean-Yves -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can not connect to printer from Vista 64 - error 0x000006f7
Great, thanks Martin. It's your own patch? But you havent tried it? Im gonna have to find an available dev machine to test on. Hopefully I can write back later with some feedback on your patch. Thanks again, Andreas Martin Zielinski wrote: Hello Andreas, this hasn't been fixed in the official releases, jet. The problem and the solution has been reported earlier. Look at: http://lists.samba.org/archive/samba-technical/2007-September/055435.html If you can compile the sources yourself, you can easily apply the fix to 3.0.38 by hand. Please report, if this works for you, too - as it hasn't been confirmed, that this solution works for others than me. Bye, Martin -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can not connect to printer from Vista 64 - error 0x000006f7
Hello. I have a problem connecting to a printer via Samba from Vista 64-bit. Samba is configured to use printers from CUPS. When I try to connect to a printer I get a error message saying Windows cannot connect to the printer. Operation could not be completed (error 0x06f7). I have managed to upload both 32 and 64-bit printer drivers from a Windows client. Connection and printing works from Win XP, Win XP 64 and Vista 32, but not Vista 64. Can anyone help me to debug or provide me with a solution? OS: Debian testing (lenny) Samba: 3.0.28-1 CUPS: 1.3.4-4 Regards, Andreas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can not connect to printer from Vista 64 - error 0x000006f7
Hello Andreas, this hasn't been fixed in the official releases, jet. The problem and the solution has been reported earlier. Look at: http://lists.samba.org/archive/samba-technical/2007-September/055435.html If you can compile the sources yourself, you can easily apply the fix to 3.0.38 by hand. Please report, if this works for you, too - as it hasn't been confirmed, that this solution works for others than me. Bye, Martin Andreas Gehrke schrieb: Hello. I have a problem connecting to a printer via Samba from Vista 64-bit. Samba is configured to use printers from CUPS. When I try to connect to a printer I get a error message saying Windows cannot connect to the printer. Operation could not be completed (error 0x06f7). I have managed to upload both 32 and 64-bit printer drivers from a Windows client. Connection and printing works from Win XP, Win XP 64 and Vista 32, but not Vista 64. Can anyone help me to debug or provide me with a solution? OS: Debian testing (lenny) Samba: 3.0.28-1 CUPS: 1.3.4-4 Regards, Andreas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can only connect after running 'wbinfo -u' or 'getent passwd', and then only for a few minutes
I used this guide to help me setup samba to authenticate using active directory. http://www.enterprisenetworkingplanet.com/netos/article.php/3487081 It worked great. Then I was trying to demonstrate it to someone, and it didn't work. I couldn't find anything I did to break it. After about an hour I retraced every step I made to set it up in the first place, and it worked again. Then a few minutes later it again stopped working. I finally traced it down to the 'wbinfo -u', and 'getent passwd' commands. Either of them will make it start allowing connections from windows clients for a few minutes. My guess is 10 minutes, but I'm not sure. Those commands work both as root, and as unprivileged users. 'nscd' is not running, and has never been running while trying to figure this out. I have tried editing nsswitch.conf to look more like the examples in the documentation than the guide I found, and that didn't make a difference at all. This is running on fedora 3 SMP samba version 3.0.10 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can not connect
I was using Samba till this morning. The samba seems running on the Unix box but I can not connect form the NT server. Can you help? The person hat supported this application left and we need help. Thanks, Doris Nagola -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can not connect to share NT_STATUS_BAD_NETWORK_NAME
I have Suse 9.1 + Samba 3.0.9 + winbind joined to a Windows 2000 AD domain MyCompany. Yesterday for some unknown reason (appears to be Win2K issue) connections to Samba and the ability to browse the domain MyCompany from Win2K/XP workstations failed but connections to the public share offered by the Win2K server were OK. Also, all Win98 workstations and were unable to reconnect to the Domain MyCompany. The Win98 workstations were reset to workgroup mode and a drive was mapped to the Win2K public share; connections to Samba shares could not be made. Samba provides the following feed back: The following commands succeed: wbinfo -u wbinfo -g getent passwd getent group net ads info (clocks within seconds) The following commands fail: filesrv1:~ # wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_BAD_NETWORK_NAME (0xc0cc) Could not check secret filesrv1:~ # smbclient //filesrv1/public -U bhohl -d 4 lp_load: refreshing parameters Initialising global parameters params.c:pm_process() - Processing configuration file /etc/samba/smb.conf Processing section [global] doing parameter workgroup = MYCOMPANY doing parameter realm = MYCOMPANY.COM doing parameter security = ADS doing parameter map to guest = Bad User doing parameter password server = 192.168.1.201 doing parameter socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 doing parameter preferred master = No doing parameter local master = No doing parameter domain master = No doing parameter wins server = 192.168.1.201 doing parameter ldap ssl = no doing parameter idmap uid = 1-2 doing parameter idmap gid = 1-2 doing parameter winbind separator = / doing parameter winbind use default domain = Yes doing parameter printer admin = @ntadmin, root, administrator pm_process() returned Yes added interface ip=192.168.1.53 bcast=192.168.1.255 nmask=255.255.255.0 Client started (version 3.0.9-1.1-SUSE). Connecting to 192.168.1.53 at port 445 session request ok Serverzone is 18000 Password: Doing spnego session setup (blob length=102) got OID=1 2 840 113554 1 2 2 got OID=1 2 840 48018 1 2 2 got OID=1 3 6 1 4 1 311 2 2 10 got [EMAIL PROTECTED] Got challenge flags: Got NTLMSSP neg_flags=0x60890215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_NTLM2 NTLMSSP_CHAL_TARGET_INFO NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP: Set final flags: Got NTLMSSP neg_flags=0x60080215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_NTLM2 NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x60080215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_NTLM2 NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH SPNEGO login failed: NT_STATUS_BAD_NETWORK_NAME session setup failed: NT_STATUS_BAD_NETWORK_NAME Please help save my Samba server! Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can not connect to SWAT
On Sat, 2003-11-08 at 16:56, lovswr1 wrote:
On Sat, 2003-11-08 at 13:09, John H Terpstra wrote:
On Sat, 8 Nov 2003, lovswr1 wrote:
Hello, Until yesterday (7 nov 03) I had a mostly working 2.27 samba
running on my redhat 9 box that I configured via SWAT. Now I can not get
back into SWAT I also (in a useless attempt to make it work) upgraded
to samba 3.0 I get the following when trying to start SWAT:
An error occured while loading http://matrix1:901/:
Could not connect to host matrix1 (port 901)
here is my /etc/hosts file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain matrix1
192.168.2.147 philip
192.168.2.145 robert
192.168.1.148 pc2
192.168.1.149 freebsd
0.0.0.0 ads.osdn.com
0.0.0.0 claria.com
0.0.0.0 www.gator.com
Also /etc/services does have the correct port 901 set up
/etc/xinetd/d/swat
description: swat is the Samba Web Administration Tool, which
# allows an administrator to configure Samba using a web
# browser interface, with the URL http://localhost:901
service swat.
{
disable = no
socket_type = stream
wait = no
protocol = tcp
only_from = matrix1
Try:
only_from = localhost
- John T.
Thanks John, but I'm still getting that can not connect host error
woohooo I got SWAT working again...it was syntax. in my /etc/services i
had swat. (the period was there of course everything else was just
looking for the four letters)
user = root
log_on_failure += USERID
server = /usr/sbin/swat
port = 901
}
/etc/pam.d/samba
#%PAM-1.0
auth required pam_nologin.so
auth required pam_stack.so service=system-auth
account required pam_stack.so service=system-auth
session required pam_stack.so service=system-auth
password required pam_stack.so service=system-auth
# added by me in a panic attempt to get swat working again on 7 nov 03
samba auth required /lib/security/pam_pwdb.so nullok shadow
samba account required /lib/security/pam_pwdb.so
I dont't know if this is related but,my trouble started yesterday after
I actually got vnc-server working. I just left it at default so it
started on matrix1:1 I went to work (yes I puched a hole through
turtlefirewall just for this) connected from my laptop at work via vnc
to the redhat box. I did not do anything then jsut logged off. when I
got home I had to reboot the redhat box becuase konq would not work.
Kept complaing aobut something like the DHOCP server or other could not
be contactacted/(connected?). Well SWAT has not worked ever since. Now
the samba 2.7 still worked with a manual start, but this morning I did a
rpm -U| to 3.0 now that too is not working Any help ir direction
pointing would be greatly appreciated.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can not connect to SWAT
On Sat, 8 Nov 2003, lovswr1 wrote:
Hello, Until yesterday (7 nov 03) I had a mostly working 2.27 samba
running on my redhat 9 box that I configured via SWAT. Now I can not get
back into SWAT I also (in a useless attempt to make it work) upgraded
to samba 3.0 I get the following when trying to start SWAT:
An error occured while loading http://matrix1:901/:
Could not connect to host matrix1 (port 901)
here is my /etc/hosts file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain matrix1
192.168.2.147 philip
192.168.2.145 robert
192.168.1.148 pc2
192.168.1.149 freebsd
0.0.0.0 ads.osdn.com
0.0.0.0 claria.com
0.0.0.0 www.gator.com
Also /etc/services does have the correct port 901 set up
/etc/xinetd/d/swat
description: swat is the Samba Web Administration Tool, which
# allows an administrator to configure Samba using a web
# browser interface, with the URL http://localhost:901
service swat.
{
disable = no
socket_type = stream
wait = no
protocol = tcp
only_from = matrix1
Try:
only_from = localhost
- John T.
user = root
log_on_failure += USERID
server = /usr/sbin/swat
port = 901
}
/etc/pam.d/samba
#%PAM-1.0
auth required pam_nologin.so
auth required pam_stack.so service=system-auth
account required pam_stack.so service=system-auth
session required pam_stack.so service=system-auth
password required pam_stack.so service=system-auth
# added by me in a panic attempt to get swat working again on 7 nov 03
samba auth required /lib/security/pam_pwdb.so nullok shadow
samba account required /lib/security/pam_pwdb.so
I dont't know if this is related but,my trouble started yesterday after
I actually got vnc-server working. I just left it at default so it
started on matrix1:1 I went to work (yes I puched a hole through
turtlefirewall just for this) connected from my laptop at work via vnc
to the redhat box. I did not do anything then jsut logged off. when I
got home I had to reboot the redhat box becuase konq would not work.
Kept complaing aobut something like the DHOCP server or other could not
be contactacted/(connected?). Well SWAT has not worked ever since. Now
the samba 2.7 still worked with a manual start, but this morning I did a
rpm -U| to 3.0 now that too is not working Any help ir direction
pointing would be greatly appreciated.
--
John H Terpstra
Email: [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can not connect to SWAT
On Sat, 2003-11-08 at 13:09, John H Terpstra wrote:
On Sat, 8 Nov 2003, lovswr1 wrote:
Hello, Until yesterday (7 nov 03) I had a mostly working 2.27 samba
running on my redhat 9 box that I configured via SWAT. Now I can not get
back into SWAT I also (in a useless attempt to make it work) upgraded
to samba 3.0 I get the following when trying to start SWAT:
An error occured while loading http://matrix1:901/:
Could not connect to host matrix1 (port 901)
here is my /etc/hosts file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain matrix1
192.168.2.147 philip
192.168.2.145 robert
192.168.1.148 pc2
192.168.1.149 freebsd
0.0.0.0 ads.osdn.com
0.0.0.0 claria.com
0.0.0.0 www.gator.com
Also /etc/services does have the correct port 901 set up
/etc/xinetd/d/swat
description: swat is the Samba Web Administration Tool, which
# allows an administrator to configure Samba using a web
# browser interface, with the URL http://localhost:901
service swat.
{
disable = no
socket_type = stream
wait = no
protocol = tcp
only_from = matrix1
Try:
only_from = localhost
- John T.
Thanks John, but I'm still getting that can not connect host error
user = root
log_on_failure += USERID
server = /usr/sbin/swat
port = 901
}
/etc/pam.d/samba
#%PAM-1.0
auth required pam_nologin.so
auth required pam_stack.so service=system-auth
account required pam_stack.so service=system-auth
session required pam_stack.so service=system-auth
password required pam_stack.so service=system-auth
# added by me in a panic attempt to get swat working again on 7 nov 03
samba auth required /lib/security/pam_pwdb.so nullok shadow
samba account required /lib/security/pam_pwdb.so
I dont't know if this is related but,my trouble started yesterday after
I actually got vnc-server working. I just left it at default so it
started on matrix1:1 I went to work (yes I puched a hole through
turtlefirewall just for this) connected from my laptop at work via vnc
to the redhat box. I did not do anything then jsut logged off. when I
got home I had to reboot the redhat box becuase konq would not work.
Kept complaing aobut something like the DHOCP server or other could not
be contactacted/(connected?). Well SWAT has not worked ever since. Now
the samba 2.7 still worked with a manual start, but this morning I did a
rpm -U| to 3.0 now that too is not working Any help ir direction
pointing would be greatly appreciated.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can not connect to SWAT
Hi,
Have you followed the information given in the Samba-HOWTO-Collection.pdf.
You can obtain it from:
http://us2.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
It has a chapter on SWAT that provides detailed information on how to get
SWAT working on your system. If that fails please get back to me.
- John T.
On Sat, 8 Nov 2003, lovswr1 wrote:
On Sat, 2003-11-08 at 13:09, John H Terpstra wrote:
On Sat, 8 Nov 2003, lovswr1 wrote:
Hello, Until yesterday (7 nov 03) I had a mostly working 2.27 samba
running on my redhat 9 box that I configured via SWAT. Now I can not get
back into SWAT I also (in a useless attempt to make it work) upgraded
to samba 3.0 I get the following when trying to start SWAT:
An error occured while loading http://matrix1:901/:
Could not connect to host matrix1 (port 901)
here is my /etc/hosts file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain matrix1
192.168.2.147 philip
192.168.2.145 robert
192.168.1.148 pc2
192.168.1.149 freebsd
0.0.0.0 ads.osdn.com
0.0.0.0 claria.com
0.0.0.0 www.gator.com
Also /etc/services does have the correct port 901 set up
/etc/xinetd/d/swat
description: swat is the Samba Web Administration Tool, which
# allows an administrator to configure Samba using a web
# browser interface, with the URL http://localhost:901
service swat.
{
disable = no
socket_type = stream
wait = no
protocol = tcp
only_from = matrix1
Try:
only_from = localhost
- John T.
Thanks John, but I'm still getting that can not connect host error
user = root
log_on_failure += USERID
server = /usr/sbin/swat
port = 901
}
/etc/pam.d/samba
#%PAM-1.0
auth required pam_nologin.so
auth required pam_stack.so service=system-auth
account required pam_stack.so service=system-auth
session required pam_stack.so service=system-auth
password required pam_stack.so service=system-auth
# added by me in a panic attempt to get swat working again on 7 nov 03
samba auth required /lib/security/pam_pwdb.so nullok shadow
samba account required /lib/security/pam_pwdb.so
I dont't know if this is related but,my trouble started yesterday after
I actually got vnc-server working. I just left it at default so it
started on matrix1:1 I went to work (yes I puched a hole through
turtlefirewall just for this) connected from my laptop at work via vnc
to the redhat box. I did not do anything then jsut logged off. when I
got home I had to reboot the redhat box becuase konq would not work.
Kept complaing aobut something like the DHOCP server or other could not
be contactacted/(connected?). Well SWAT has not worked ever since. Now
the samba 2.7 still worked with a manual start, but this morning I did a
rpm -U| to 3.0 now that too is not working Any help ir direction
pointing would be greatly appreciated.
--
John H Terpstra
Email: [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] can not connect to the shared printer
I'm not an expert but I see lots of things missing in your smb.conf file. You have not defined the samba server netbios name. No samba password path. Have you set samba passwords? Define security level. Also, you may find that you will neeed to stop IPChains and IPTables on the samba server once you get things running somewhat. At least until you can set up firewall rules. Once you set the netbios name - you should then be able to see the samba server in network neighborhood. Also, should be alble to ping from windows both the samba IP address and net bios name. These are all things I learned over the last few months as I have been learning Samba - hope it helps. Tom Winfield [global] workgroup = HOME netbios name = linux-server server string = Tom's Linux Server hosts allow = 192.168.0. 127. guest ok = yes log file = /var/log/samba/%m.log log level = 1 max log size = 100 security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = yes browsable = yes domain master = no preferred master = no wins support = yes dns proxy = no -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Xiaodong Zhang Sent: Monday, December 23, 2002 10:24 AM To: [EMAIL PROTECTED] Subject: [Samba] can not connect to the shared printer Hi there, I'm learning Samba and I really appreciate somebody out there can help me out. I'm using RedHat advanced server and a windows 2000. I created a workgroup on samba and only samba machine and win2k machine are members. I shared the printer attached to the Linux. From win2k PC, I can see the workgroup, but I can not find the samba host from the workgroup, nor does the printer. The smb.conf is attached. I run smbclient -NL hostname and it shows the printer under the Sharename. If I run net view //hostname, it returns that: System error 53 has occured, the network pass was not found I setup the samba 2 days ago, and the same problem happened then and now. BTW, I can mount a windows share from Linux, so I guess samba is running. Thanks and merry Christmas. Xiaodong -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] can not connect to the shared printer
Hi there, I'm learning Samba and I really appreciate somebody out there can help me out. I'm using RedHat advanced server and a windows 2000. I created a workgroup on samba and only samba machine and win2k machine are members. I shared the printer attached to the Linux. From win2k PC, I can see the workgroup, but I can not find the samba host from the workgroup, nor does the printer. The smb.conf is attached. I run smbclient -NL hostname and it shows the printer under the Sharename. If I run net view //hostname, it returns that: System error 53 has occured, the network pass was not found I setup the samba 2 days ago, and the same problem happened then and now. BTW, I can mount a windows share from Linux, so I guess samba is running. Thanks and merry Christmas. Xiaodong # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2002/12/23 10:01:26 # Global parameters [global] workgroup = XGROUP server string = Birch Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log max log size = 500 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No printing = lprng [homes] comment = Home Directories valid users = %S read only = No create mask = 0664 directory mask = 0775 browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hpdeskjet940c] comment = HP Deskjet 940c attached to Birch path = /var/spool/samba guest account = zhangx read only = No guest ok = Yes printable = Yes printer name = hpdeskjet940c oplocks = Yes share modes = Yes
Re: [Samba] can not connect to the shared printer
On Mon, 2002-12-23 at 16:23, Xiaodong Zhang wrote: Hi there, Hi, I'm learning Samba and I really appreciate somebody out there can help me out. I'm using RedHat advanced server and a windows 2000. I created a workgroup on samba and only samba machine and win2k machine are members. I shared the printer attached to the Linux. From win2k PC, I can see the workgroup, but I can not find the samba host from the workgroup, nor does the printer. The smb.conf is attached. I run smbclient -NL hostname and it shows the printer under the Sharename. If I run net view //hostname, it returns that: System error 53 has occured, the network pass was not found I setup the samba 2 days ago, and the same problem happened then and now. BTW, I can mount a windows share from Linux, so I guess samba is running. The fact that you can mount a samba share from Linux means nothing, this is not dependant upon whether you have the smbd running. This is so you dont have to have smbd running on every client machine (there are mixed OS networks). The mount command using the -t smbfs depends totally on whether the smbfs was compiled into the kernel under File Systems. The way to test whether the daemon is running would be to run: ps aux | grep smbd This should show you whether the smbd is running. If it is try restarting it and looking in the Samba logs for any errors, if it isnt then look it up. Thanks and merry Christmas. Xiaodong HTH and a Merry Christmas to you (if you celebrate it), Shak # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2002/12/23 10:01:26 # Global parameters [global] workgroup = XGROUP server string = Birch Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log max log size = 500 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No printing = lprng [homes] comment = Home Directories valid users = %S read only = No create mask = 0664 directory mask = 0775 browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hpdeskjet940c] comment = HP Deskjet 940c attached to Birch path = /var/spool/samba guest account = zhangx read only = No guest ok = Yes printable = Yes printer name = hpdeskjet940c oplocks = Yes share modes = Yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CAN`T CONNECT SAMBA - W98
Hi Redhat 7.2 - SMB running W98 II I can ping IP address in both ways. In Linux, I can ping the NetBIOS name , but from W98 he cannot find the NetBIOS name o Linux. How caan I solve this? Looking forward Best Regards -- Dâmaso Constantino LABORATORIOS MUÑOZ CARO, S.L. Av. de Europa, 30 28023 MADRID ESPAÑA Tel.: +34 91 351 42 02 Fax: +34 91 351 34 38 E-Mail general: [EMAIL PROTECTED] E-Mail personal: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
