Well, This is the 3rd time I install Suse 9.1 Pro since last friday and still some serious problems when mapping to a Samba server. It asks for the username and password then "The process for smb;//xxxx protocol died unexpectedly. What can cause this ? -- Luis-M.
I have the same problem, but found windbind (yast, system, runlevel editor) needed to be started, but without windbind, I could not even browse the domain. I have a thread also on the list, but have not received any further info. I am going to try to make a new user with logon and password the same as the winwk domain and see what happens. We also have a domain controller on our network. Art Luis-Miguel Astudillo wrote:
Well,
This is the 3rd time I install Suse 9.1 Pro since last friday and still some serious problems when mapping to a Samba server.
It asks for the username and password then "The process for smb;//xxxx protocol died unexpectedly. What can cause this ?
Hi Art, Well Winbind wasn't installed so I installed throught Yast. Then when I tried to enable the service it told me that etc/smb.conf was not configured. Installed Samba server and now get the following error : Internal Error - Please send a full bug report at http://bugs.kde.org. Unknown error condition in stat: Network is unreachable... Well this version of Suse 9.1 Pro sucks so far !! Luis-M Art Fore wrote:
I have the same problem, but found windbind (yast, system, runlevel editor) needed to be started, but without windbind, I could not even browse the domain. I have a thread also on the list, but have not received any further info. I am going to try to make a new user with logon and password the same as the winwk domain and see what happens. We also have a domain controller on our network.
Art
Luis-Miguel Astudillo wrote:
Well,
This is the 3rd time I install Suse 9.1 Pro since last friday and still some serious problems when mapping to a Samba server.
It asks for the username and password then "The process for smb;//xxxx protocol died unexpectedly. What can cause this ?
Luis-Miguel Astudillo wrote:
Hi Art,
Well Winbind wasn't installed so I installed throught Yast. Then when I tried to enable the service it told me that etc/smb.conf was not configured.
Installed Samba server and now get the following error : Internal Error - Please send a full bug report at http://bugs.kde.org. Unknown error condition in stat: Network is unreachable...
Well this version of Suse 9.1 Pro sucks so far !!
Not really so. Check in /etc/samba/smb.conf that you have workgroup = your_domain_name Also, go to KDE Control Center, Internet & Network, Local Network Browsing and input your Windows domain username.
Hi Silviu, 1. smb.conf is properly configured 2. KDE Control center has been properly configured What els has to be done for it to be operational ????? I have been using Suse since v8.1 and NEVER has such dumb problems. Since I received v9.1 Pro, I only see problems with ACPI, LCD screen size that keeps asking at every single login, Samba & Windows domain browsing and 9.1 leaves less free memory on my system for other tasks. Still I haven't tried VMWare 4.5.1 workstation yet till all other problems are resolved if there is any memory left to run it. All of these configurations are unnecessary on distros like Xandros (all versions) and others since they see all of the windows workgroups automatically. If I don't finalize this problem today I will has for a refund from Suse since I don't have time to fiddle with the system anymore. When I paid for a product I expect it to run of the shelf. Luis-M. PS. My laptop as 768Mb of RAM and mosft of my PCs have a 1Gb of RAM. Silviu Marin-Caea wrote:
Luis-Miguel Astudillo wrote:
Hi Art,
Well Winbind wasn't installed so I installed throught Yast. Then when I tried to enable the service it told me that etc/smb.conf was not configured.
Installed Samba server and now get the following error : Internal Error - Please send a full bug report at http://bugs.kde.org. Unknown error condition in stat: Network is unreachable...
Well this version of Suse 9.1 Pro sucks so far !!
Not really so.
Check in /etc/samba/smb.conf that you have workgroup = your_domain_name
Also, go to KDE Control Center, Internet & Network, Local Network Browsing and input your Windows domain username.
Tried that, no difference, although I after I did put the infor in control center, I did not need winbind anymore. Now when I access datacenter, I put in the logion and password, the URL bar shows smb://art_fore@datacenter/ but comes with with datacenter protocol died unexpectedly. Also can no longer join the domain with samba client. I would like to see someone who has this working put the following info on the mail list so I and others who have not gotten it to work could compare setups. Following info should be inclued: 1. Is network controled by Active Domain controler or not, or is the server a standalone computer with shares enabled. 2. Is samba server being used? 3. Is Samba client being used? 4. Is Kerbos being used? 5. Is PAM being used? 6. What steps did you go through to get system operating? 7. Do you have password entried in the /etc/sdamba/smbpasswd file? This kind of info would help what appears to be alot of people having problems with samba? Art Silviu Marin-Caea wrote:
Luis-Miguel Astudillo wrote:
Hi Art,
Well Winbind wasn't installed so I installed throught Yast. Then when I tried to enable the service it told me that etc/smb.conf was not configured.
Installed Samba server and now get the following error : Internal Error - Please send a full bug report at http://bugs.kde.org. Unknown error condition in stat: Network is unreachable...
Well this version of Suse 9.1 Pro sucks so far !!
Not really so.
Check in /etc/samba/smb.conf that you have workgroup = your_domain_name
Also, go to KDE Control Center, Internet & Network, Local Network Browsing and input your Windows domain username.
Well folks I added the //idmap gid/ = 10000-20000 and ///idmap uid/ = 10000-20000 as per the documentation and well guest what !!! IT STILL doesn't work. The more I read this thread the more I figure that Suse pushed this version 9.1 out the door just to keep everyone happy. / Luis-M. Art Fore wrote:
Tried that, no difference, although I after I did put the infor in control center, I did not need winbind anymore. Now when I access datacenter, I put in the logion and password, the URL bar shows smb://art_fore@datacenter/ but comes with with datacenter protocol died unexpectedly. Also can no longer join the domain with samba client.
I would like to see someone who has this working put the following info on the mail list so I and others who have not gotten it to work could compare setups. Following info should be inclued:
1. Is network controled by Active Domain controler or not, or is the server a standalone computer with shares enabled.
2. Is samba server being used?
3. Is Samba client being used?
4. Is Kerbos being used?
5. Is PAM being used?
6. What steps did you go through to get system operating?
7. Do you have password entried in the /etc/sdamba/smbpasswd file?
This kind of info would help what appears to be alot of people having problems with samba?
Art
Silviu Marin-Caea wrote:
Luis-Miguel Astudillo wrote:
Hi Art,
Well Winbind wasn't installed so I installed throught Yast. Then when I tried to enable the service it told me that etc/smb.conf was not configured.
Installed Samba server and now get the following error : Internal Error - Please send a full bug report at http://bugs.kde.org. Unknown error condition in stat: Network is unreachable...
Well this version of Suse 9.1 Pro sucks so far !!
Not really so.
Check in /etc/samba/smb.conf that you have workgroup = your_domain_name
Also, go to KDE Control Center, Internet & Network, Local Network Browsing and input your Windows domain username.
I tried using the ADS with kerberos instead of Domain and used the comman line per the samba documentation. Still cannot get on the domain or anything. It seems it does not authenticate, but kinit shows that it does. Am going on the sama list and see if I have any luck there. Art Luis-Miguel Astudillo wrote:
Well folks I added the //idmap gid/ = 10000-20000 and ///idmap uid/ = 10000-20000 as per the documentation and well guest what !!!
IT STILL doesn't work.
The more I read this thread the more I figure that Suse pushed this version 9.1 out the door just to keep everyone happy. /
Luis-M.
Art Fore wrote:
Tried that, no difference, although I after I did put the infor in control center, I did not need winbind anymore. Now when I access datacenter, I put in the logion and password, the URL bar shows smb://art_fore@datacenter/ but comes with with datacenter protocol died unexpectedly. Also can no longer join the domain with samba client.
I would like to see someone who has this working put the following info on the mail list so I and others who have not gotten it to work could compare setups. Following info should be inclued:
1. Is network controled by Active Domain controler or not, or is the server a standalone computer with shares enabled.
2. Is samba server being used?
3. Is Samba client being used?
4. Is Kerbos being used?
5. Is PAM being used?
6. What steps did you go through to get system operating?
7. Do you have password entried in the /etc/sdamba/smbpasswd file?
This kind of info would help what appears to be alot of people having problems with samba?
Art
Silviu Marin-Caea wrote:
Luis-Miguel Astudillo wrote:
Hi Art,
Well Winbind wasn't installed so I installed throught Yast. Then when I tried to enable the service it told me that etc/smb.conf was not configured.
Installed Samba server and now get the following error : Internal Error - Please send a full bug report at http://bugs.kde.org. Unknown error condition in stat: Network is unreachable...
Well this version of Suse 9.1 Pro sucks so far !!
Not really so.
Check in /etc/samba/smb.conf that you have workgroup = your_domain_name
Also, go to KDE Control Center, Internet & Network, Local Network Browsing and input your Windows domain username.
Hi Hi was having an similar problem as you, in my case I was trying to access a share in my windows xp machine and I would get the same error as you. The problem was that I needed to have an account in suse 9.1 with the same username and the same password in windows xp too. I tried and it worked... Cumprimentos Jose Silva -----Original Message----- From: Luis-Miguel Astudillo [mailto:lm.astudillo@sc-aigs.com] Sent: quarta-feira, 19 de Maio de 2004 20:47 To: suse-linux-e@suse.com Subject: [SLE] Suse 9.1 and Samba Client Well, This is the 3rd time I install Suse 9.1 Pro since last friday and still some serious problems when mapping to a Samba server. It asks for the username and password then "The process for smb;//xxxx protocol died unexpectedly. What can cause this ? -- Luis-M.
participants (4)
-
Art Fore -
Jose Silva -
Luis-Miguel Astudillo -
Silviu Marin-Caea