similar to: tree connect fail

"Chris R. Martin" wrote: > > I upgraded my samba package to frozen (2.0.6), and now it doesn't work with > my old smb.conf file. I've been up and down the samba docs and I've tried > all sorts of options which don't seem to have any effect (which probably > means I'm missing something basic). I can't even list the shares on the > server itself:

OS=Free BSD 4.4 with Samba 2.2.2 installed via source. System has 2 IP's one internal one external. I am telling samba to bind to xl0 which is my internal network. The samba system has an IP of 192.168.1.1 ------------------------------------------------------------------------ ---------------------------------------- su-2.05# nmblookup 192.168.1.1 INFO: Debug class all level = 3 (pid 96313

I previously had an older version of Samba installed with the following smb.conf: ; Make sure and restart the server after making changes to this file, ex: ; /etc/rc.d/init.d/smb stop ; /etc/rc.d/init.d/smb start [global] ; Uncomment this if you want a guest account guest account = nobody log file = /var/log/samba-log.%m lock directory = /var/lock/samba share modes = yes

Hi, I've been using samba for a while now with relatively simple configurations. I do however have a few questions: * When using encrypted passwords with samba, is it possible to authenticate users using the Unix user password(/etc/passwd)? * When using smbclient I get the error NT_STATUS_LOGON_FAILURE: added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0 Password:

I'm just about to give up in despair of getting Samba working on my network. I've browsed through several books, HOWTOs and websites and still can't figure out what I'm doing wrong. Before I quit, could someone double check this and maybe spot what I've missed? First, let me describe my network. Names and IP addresses have been changed to protect the innocent. :-)

Hi, I don't know why smbmount doesn't work. My samba version is 3.0.0. Remote server (192.168.1.1) is running samba 3.0.0 too. Both are linux machines. 1) If I try to mount a existing share i get this /usr/local/samba/bin/smbmount //192.168.1.1/PAVFN /monta added interface ip=192.168.1.200 bcast=192.168.1.255 nmask=255.255.255.0 Password: smbfs/init_mount: execv of smbmnt failed.

Hi all, I have network with few win 95/xp machines and suse 9.3 prof server. On every win client is installed RealPopup (RealPopup homepage: www.realpopup.it). I can send popup message from my xp computer to win 95, and I can get reply on new message addressed from win 95 computer, so looks like popup communication works well. If I use: server:~ # echo "test" | smbclient -M bane

Hello list, I don't know what is breaking my samba box but I am really very worried and confused !! My samba server has no problem with linux client. "smbclient -L <samba IP> -U <samba user>" runs well. No problem at all. But whenever I try to access the shares from Win-XP it reports that "path not found". And after repeatedly trying the same Win-XP

FROM NT \\firewall.surson runs perfectly WHY??? root@firewall init.d]# ./smb status smbd (pid 12183) est? rodando... nmbd (pid 1397) est? rodando... [root@firewall init.d]# smbclient //firewall.surson/profile -Ucatena%motpock added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0 Domain=[SURSON] OS=[Unix] Server=[Samba 2.2.3a] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Hi there, Im using for long time winbind + squid for my proxy server and it has been working very good... No problems at all. Some months ago, I decided to get rid of Netbios protocol and start to use only dns for name resolution on my domain. That's when my problem begin. All my windows servers and workstations are doing fine without netbios but I cant get winbind to work without

Hi, I've been trying unsuccessfully over the past couple of days to get my windows machines to recognize my linux box. I've been working through the troubleshooting guides I can't get the query of the client machine to work using the broadcast address: I have the following 3 machine network: lifebook SUSE 192.168.1.100 renegade WXP 192.168.1.101 maverick W2K

Hi I have installed samba-2.2.7a and cups-1.1.18. After reading all the documentation samba provides as well as the cups administrators guide I am still stuck. I have added the printers just the way the samba and cups documentation says. Anyway here is my output from cupsaddsmb, It fails on the last step, so i have run that manually again afterwards with debugging enabled. I believe this to be

I have two computers ROLAND (RedHat 5.2 and Samba) and LINDA (Windows95). I am already able to print on the printer connacted to LINDA. Yesterday, before I managed to get the printer working, I was alos able to see ROLAND's directory 'tmp' and 'winD' on LINDA. The problem that I saw this morning was that the printing still works but LINDA can no longer see the shares of

Ahh, many sleepless nights spent on a stinky Windows 98 box! I'm using Samba 2.2.0 with Red Hat Linux 7.1, and am having trouble resolving the samba server. I went through the "fault tree" in the "Using Samba" book, and this was the section I got stuck on. Do I need to be running a name server besides nmbd? nmblookup returns some results: ----------8<----------

Hi folks, I'm trying to access a share on a RedHat 9 server from a Fedora Core 1 workstation. Here is the environment (pretty vanilla), the error I'm getting, and what I've done to try hunt down the problem. Server, 192.168.1.100, has a share of /home/users/herman Workstation, 192.168.1.101, has a mount point of /home/herman/serverdata smb.conf on server has [global] hosts deny =

I posted the message below, some time ago, and haven't got any suggestions yet. I would be most grateful if anyone could tell me how I can increase the timeout period for setting up NETBIOS Sessions for smbclient, as this would perhaps solve the problem. By the way, there is no problem when printing from any Windows machine. PREVIOUS MESSAGE FOLLOWS I have been trying to use Samba 2.2.6

Hello everyone! I've searched the archives and seen this problem crop up a couple of different times. None of the solutions I've found seemed to have worked. Here's the synopsis: I've recently installed FC4 and samba shares for home directories should work right out of the box. Default settings, etc... I get this error: sohmc@bart:~$ smbclient //127.0.0.1/sohmc added

I did it more then 12 times... I have a lot of problems with winbind and NEVER I did receive a answer... Sorry if I have a poore english: I hve 3 installations with problems... I never saw this I think that Im not a god SAMBA Administrator but I did read all the doc.... I dont have any troubles with other soft, but with samba ehehehehehe I did send e-mails to the lis in : 11/3. 12/3, 16/3,

I'm stumped on getting Samba to work again on our small network. I've got one Windows 95 machine that started to refuse to talk to Samba last week. I *was* running one of the 1.9.18 releases, but when it stopped working, I figured I would delete the old release and do a clean install of 2.0.3. I've done that, and used SWAT to configure the smb.conf file (which can be seen below).

hi, we recently upgraded from samba 2.2.8a w/ldap to samba3 w/ldap and having troubles with domain group mappings. first symptom is that net groupmap list returns nothing. [root@lola root]# net groupmap list [root@lola root]# if we try to add a groupmapping, the command fails: net groupmap add sid=<sid-gid> ntgroup="Domain Admins" unixgroup=domadm type=domain --debuglevel=4