similar to: Called name not present

Believe me, I have tried everytbing I can think of to solve this problem. I will work my tail off to resolve this but I am fresh out of ideas. Any suggestions would be GREATLY appreciated. Here are the details... problem: server can see machines/shares on clients but clients cannot see machines/shares on server workgroup/domain: golgerth no router server: rpms: kernel 2.4.18.19.8.0

PROBLEM: Cross-subnet browsing is not working. Browse lists on all machines contain only the machines on the local subnet. SUMMARY OF ANALYSIS: The Local Master Browser (LMB) running Windows XP (ZAYIN) never contacts the Domain Master Browser (DMB) running Samba (BETH) to initiate a synchronization of browse lists.

Hi, I am trying to list the shares on a windows ME machine and I am getting the following [root]# smbclient -L 192.168.0.253 added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 session request to 192.168.0.253 failed (Called name not present) session request to 192 failed (Called name not present) session request to *SMBSERVER failed (Called name not present) I have also tried

I've got a Samba 3 box running RHEL 3 that has been added to a Windows 2000 domain as a member server, however it cannot be browsed via the network (it appears within the domain, but does not open the machine). Its IP address is 10.30.4.1/255.255.252.0, nbtstat.exe on one of the windows boxes returns as below P:\>nbtstat -A 10.30.4.1 Local Area Connection 3: Node IpAddress: [10.30.5.1]

Hi! Yesterday it was working very good, but today: # /usr/local/samba/bin/smbclient -L 192.168.0.11 added interface ip=192.168.0.100 bcast=192.168.0.255 nmask=255.255.255.0 session request to 192.168.0.11 failed (Called name not present) session request to 192 failed (Called name not present) session request to *SMBSERVER failed (Called name not present) 192.168.0.11 - PC with Win98; all

Hi there. This is with regards to samba-3.0.23c, on FreeBSD 6.0-RELEASE-p12 Previously I had Samba up and running without any problems. Then I decided to do a tiny upgrade by simply switching to a new motherboard, while keeping all other hardware and software aspects the same. However, after the upgrade, netbios name resolution seems to have stopped working somehow. \\servername lookups no

Hello, I just took an old PC and installed SuSE 7.0 on it. The machine has 32Mb of RAM, so I needed a slim installation and kernel, and this was the only package I could get to install without immense effort (I tried 5 other versions of small linux distros from linuxiso.org before this one). The version of Samba I installed on this Suse box is 2.0.7. From what I have read, this version SHOULD

I don't know what information would be helpful. I will give some but also try not to waste bits. I am using LDAP. My username is 'davt01'. I am able to login to my samba pdc just fine. I get these logs when I try to access //server/foobar. Also see below for some relevant configs: [2004/01/28 15:14:37, 3] auth/auth.c:check_ntlm_password(265) check_ntlm_password: sam

HELLO ! I HAVE SOME STRANGE PROBLEMS AND I NEED HELP. I DIDN'T FIND SIMILAR PROBLEMS IN THE MAILING LIST, SO POSSIBLY I HAVE OVERLOOKED SOMETHING VERY SIMPLE. WHAT I USE *********** SOLARIS 8; SAMBA 2.2.2 (DEFAULT COMPILATION AND INSTALLATION) WIN-BOXES: WIN2K (NATIVE INSTALLATION AND SOME WITH SP2); WINNT4; ALL MS-BOXES POINT TO THE SAMBA SERVER AS A WINS SERVER TWO WORKGROUPS IN

Hi, After lots of struggle and rtfm I finally got most things running, except for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but plenty more to learn. Here's the setup in summary: system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master, wins server, domain master browser, no iptables; system bdc is the BDC on subnet 192.168.2.0,

Hi everyone, I'm trying to set up a Windows XP Pro client to connect to a Samba server (version 2.2.8) on a Redhat 8.0 linux box, but have been having trouble for the past 3 days. I have gone through Troubleshooting Samba at [http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf] but I can't figure out how to fix the problem. I suspect that the broadcast address may not be the same on both

Hello! I've got a problem connecting my Linux Mandrake 8.0 box running samba-2.2.0-5mdk to a Windows server. I've been given the IP-Adress, Sharename and username: IP\Share: \\164.56.65.199\transfer Username: John Doe (Note: It's not really "John Doe", but another name, but also with a blank.) There's no password.

Hi! I so far succeeded in setting up a Samba NT4 DC with OpenLDAP backend. Unfortunately I get the following error message connecting a Windows XP client to the domain (translated from german): [...] The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.lohrmann.de [...] This is surely due to a

Hello list, The issue is as the topic says, following are details: the Samba server running as ADS member, NBT enabled on Windows machines, no WINS. Windows machines can find each other by 'nbtstat -a' but cannot find the Samba server. The Samba server can't find neither Windows machines nor itself by 'nmblookup -a <netbios-name>', error message is "could not open

All, 1. Here is my network configuration: One NT4 PDC One NT4 BDC Two Sun boxes, both configured as Domain Member servers running Samba version 3.0.10 providing file and print sharing. Three Windows 2000 boxes configured as Citrix servers Two Sun boxes configured as Sun Ray servers (used in conjunction with the Citrix servers) One UNIX box used as a DNS Master Server One UNIX box used

Hi all, I have a Solaris 2.7 host with a recent install of samba-2.2.2. I am using an smb.conf from a simmilar host that works perfectly. I can't seem to connect to the host with Samba. I am getting: ########## //g4syd/usr/local/samba/bin 634 # smbclient -d 4 -L g4syd added interface ip=10.1.5.7 bcast=10.1.5.255 nmask=255.255.255.0 Client started (version 2.2.2). resolve_hosts: Attempting

> > > Adding pdc1 to the hosts file (c:\windows\system32\drivers\etc\hosts) > did > not make a difference. After adding pdc1 to lmhosts, "net use > \\pdc1" did > work. So in the case of pdc1 one, the name is being resolved as a > netbios > name (i.e. via lmhosts) not a tcp/ip type name (i.e. via dns or hosts) > > But then why does "net

I use Samba 3.14.17 and later test Samba 3.6.9. The computer is WINs server on Samba. wins support = yes All work good. But now I see that NetBIOS clients cannot to re-register their names on WINs, when he change IP. >From WinXP SP3 I do nbtstat -RR Answer: NetBIOS-names registered by this computer were changed. >From server: relay2# nmblookup -U 10.0.0.1 -R -S aiy querying aiy on

other machine with the details listed above. Windows NT doesn't prompt me for a password, and I can create/read/delete... files. Now I'd like to connect to the machine using Linux. So I tried: [root@fp-2252 /etc]# mount -t smbfs -o username=John\ Doe //164.56.65.199/transfer /mnt/Transfer 20313: session request to 164.56.65.199 failed (Called name not present) 20313: session

Hi everybody ! Here is what I do : ---------------------------------------------------------------- [gui@r52h153 gui]$ nmblookup -A 128.61.107.78 Looking up status of 128.61.107.78 EL PRESIDENTE <00> - B <ACTIVE> THETAXI <00> - <GROUP> B <ACTIVE> EL PRESIDENTE <03> - B <ACTIVE> [gui@r52h153 gui]$