Displaying 5 results from an estimated 5 matches similar to: "Samba error message"
2003 Dec 11
0
"Errror - group names should not be multihomed."
Hello,
I'm getting these errors on a samba 2.2.8a wins server in a NT4 network:
[2003/11/25 09:41:00, 0] nmbd/nmbd_winsserver.c:wins_process_multihomed_name_registration_request (1022)
wins_process_multihomed_name_registration_request: group name
registration request received for name DOMAIN<00> from IP 192.168.10.5 on
subnet WINS_SERVER_SUBNET. Errror - group names should not be
2003 Jul 11
0
Subject: WINS for a NAS (group names should not be multihomed)
we use a Samba 3.0.0beta2 as a PDC (node name 'TESTPDC', domain name
'MYDOMAIN') and WINS server
=-=-=-=-=-
# grep -i wins smb.conf
wins support = yes
-=-=-=-=-=
we also use a NetApp Filer F87 (netBIOS name 'JUPITER') configured
- with only one nw interface, with an IP number shown here as ((NAS_IP))
- to join a CIFS domain (no problem for now), and registered
2009 Jun 05
2
I am so frustrated - Samba ports not opening and no error message
Okay - I've been plugging away and it got to the point that running
smbclient was returning information about an Alfresco install that I
never used, so I went ahead and deleted everything I could find on my
machine that said "alfresco". I then removed samba using apt-get from
the machine by typing
apt-get remove --purge samba
I deleted the /etc/samba directory and re-installed
2004 Feb 10
1
samba, RedHat and Windows XP Home
Howdy. I'm running samba-3.0.2-2 (from the binaries on samba.org) on a
RedHat 9 box with kernel 2.4.20-28.9.
I can access shares from my Windows XP Home box, but the performance
isn't very good. When I looked into this, I discovered that apparently
the connections are getting dropped, over and over again, which causes a
lot more work, I'm sure. Here's a snippet from my main
2008 Feb 19
3
Problem connecting to Samba server
Hi
Clients cannot connect to the Samba server (Version 3.0.25b OpenBSD/amd64), first attempt gives Access denied, second attempt gives The network name request is no longer available.
Can someone please help in finding out what is wrong? I've been going through the logs and configuration the past week, but can't seem to find out what's the issue. Any pointers would be appreciated.