search for: aclient

Everything else works, but "nmblookup -B ACLIENT '*'". It shows the servers IP address, unless "ACLIENT" can be resolved thru hosts/dns. Can someone explain me why? Samba 2.0.5b on Linux 2.0.36 name resolve order = lmhosts host wins bcast dns proxy = No wins proxy = No wins server = mywinsserver.mydomain wins support...

Hello everyone. I apologize in advance for a simple question yet hard to a beginner. I'm new to SAMBA - 1 1/2 days old. I'm in the process of configuring/testing SAMBA in our RISC test box. I am now stuck on TEST 5 below. TEST 5:-------run the command "nmblookup -B ACLIENT '*'"You should get the PCs IP address back. If you don't then the clientsoftware on the PC isn't installed correctly, or isn't started, or yougot the name of the PC wrong. If ACLIENT doesn't resolve via DNS then use the IP address of theclient in the above test. Exac...

...e and windows 95 on another but i am unable to see the linux machine in my windows pcs network neighborhood.to check my samba server i tried the tests given in DIAGNOSIS.txt.I am able to run tests 1 to 4 without error but in test 5 which says ::: "test 5 : run the command "nmblookup -B ACLIENT '*'" You Should Get The PCs IP Address Back.If you don't then the client software on the PC is not installed correctly,or is not started ,or you got the name of the pc wrong. if ACLIENT doesnot resolve via dns then use the ip address of the client in the above test." sir i...

has anyone tried to make a win98 (beta3) connect to a samba server? Is there some little secret I don't know about? -Steve Schwartz steve@photographics.net

I want to share my linux printer with my windows laptop. The printer is attached to box with redhat 7.2 and samba-2.2.1a-4. The laptop runs windows 98 and they are connected by a netgear RP114 router. I have been following DIAGNOSIS.txt. I had trouble with the test 2, "ping ACLIENT" and "ping BIGSERVER" until I added ACLIENT to /etc/hosts on BIGSERVER and added BIGSERVER to \windows\hosts on ACLIENT. Tests 3-6 were fine but I had to run smbpasswd -a <accountname> to get through test 7. I'm stuck on test 8, "net view \\BIGSERVER". When I tr...

...---- Workgroup Master --------- ------- # /usr/xpg4/bin/date -u;/opt/csw/bin/nmblookup -B AEQUITAS __SAMBA__ Sat Jul 12 22:52:47 GMT 2008 querying __SAMBA__ on 192.168.35.147 192.168.35.147 __SAMBA__<00> # /usr/xpg4/bin/date -u;/opt/csw/bin/nmblookup -B ACLIENT '*' Sat Jul 12 22:53:29 GMT 2008 querying * on 0.0.0.0 192.168.35.42 *<00> # /usr/xpg4/bin/date -u;/opt/csw/bin/nmblookup -B ACLIENT '*' Sat Jul 12 22:53:45 GMT 2008 querying * on 0.0.0.0 192.168.35.42 *<00> # /usr/xpg4/bin/date -u;/opt/csw/bin/nmblookup -d 2 '*'...

...Master --------- ------- RABNETWORK BEASTIE 4) works: *nmblookup -B BIGSERVER __SAMBA__ amanda@beastie:~$ nmblookup -B BEASTIE __SAMBA__ querying __SAMBA__ on 127.0.0.1 192.168.1.102 __SAMBA__<00> *5) fails:* nmblookup -B ACLIENT '*'** amanda@beastie:~$ nmblookup -B presta '*' querying * on 0.0.0.0 192.168.1.102 *<00> I'm stopping here because it seems pretty clear that the Windows XP client machines are hating me.Where do I go from here? Thanks, Amanda *

Hi , I am using Mandrake 7.2 and trying to install samba to share my linux hard disk with Windows 98 ... Herewith my config and diagonstics : bigserver <------------> aclient runing : mandrake 7.2 Win98 Ip Addr.: 192.168.0.1 192.168.0.2 password encrypted activated activated - ping commands work fine on both ways, so my Tcp/ip connection is ok - I did testparm, no error - smb.conf file based on sample - netbios-ssn port...

...an email saying "it doesn't work" and you have not >followed this test procedure then you should not be surprised if I >ignore your email. > > >ASSUMPTIONS >----------- > >In all of the tests I assume you have a Samba server called BIGSERVER >and a PC called ACLIENT both in workgroup TESTGROUP. I also assume the >PC is running windows for workgroups with a recent copy of the >microsoft tcp/ip stack. Alternatively, your PC may be running Windows >95 or Windows NT (Workstation or Server). > >The procedure is similar for other types of clients. &gt...

...trying to connect to it from a Win95 machine, and it fails. If I try to use smbclient from a different Unix host, it connects fine. If we look at a Win/NT machine, the Sparc server comes up on the browse list, but we can't see any of the shares. In Test 5, it talks about using nmblookup -B ACLIENT '*' to check things out, and it can find the Win/NT machine, but it can't the Win95... The server itself is on subnet 96, the Unix host I can talk to is on subnet 2, the Win/NT server is on subnet 137, and the Win95 is on subnet 32 (we have a B class)... Since the Win/NT Browser see...

...up Samba (2.0.3). After configuring it to act as a PDC, WINS server, and master browser, I fired it up. Everything seems to be working fine, except no Windows clients can see the Samba server via Network Neighborhood, ping, or Find Computer. Samba passed tests 1,3,4,5 (for the other Samba server as ACLIENT), 6 (for the Samba servers), and 7. The Windows clients can see all the other machines (including the older Samba server), so I am assuming the Samba server is providing master browser services (and log.nmb reports that it is the domain and local master browser). smb is reporting no errors all the...

...but also returned several lines thus: tdb((null)): tdb_open_ex: could not open file /var/cache/samba/unexpected.tdb: No such file or directory On inspection, the unexpected.tdb file does not exist, and I don't know where to get it or whether it is important! TEST 5: ------- "nmblookup -B ACLIENT '*'" Successfully return the IP address, but also returned the same error lines as test 4. TEST 6: ------- "nmblookup -d 2 '*'" Error lines from Test 4 + name_query failed to find name * TEST 7: ------- "smbclient //BIGSERVER/TMP" Anonymous login successfu...

...I'm having a problem in that each day the company must re-enter the Sage serial number to re-register the product. Having done this the package will work correctly for the remainder of the day. The Sage support team have informed me that this is caused by time settings on the file "aclient.dbf" and directed me to this link http://www.oreilly.com/catalog/samba/chapter/book/ch08_01.html After adding the options below the problem remains. Dos filetimes = yes Dos filetime resolution = yes Sage are not willing to modify their package as it doing exactly what it's mean...

...--------- ------- T A308 WKG DZTI 4 --------------------------- [root@fc9 ~]# nmblookup -B fc9 __SAMBA__ querying __SAMBA__ on 127.0.0.1 10.10.10.99 __SAMBA__<00> 5 --------------------------- [root@fc9 ~]# nmblookup -B ACLIENT '*' querying * on 10.10.10.255 10.10.10.99 *<00> 6 --------------------------- [root@fc9 ~]# nmblookup -d 2 '*' added interface eth0 ip=fe80::216:e6ff:fe31:e989%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff:: added interface eth0:1 ip=10.10.10.99 bcas...

...ter >configuring it to act as a PDC, WINS server, and master browser, I fired >it up. Everything seems to be working fine, except no Windows clients >can see the Samba server via Network Neighborhood, ping, or Find >Computer. Samba passed tests 1,3,4,5 (for the other Samba server as >ACLIENT), 6 (for the Samba servers), and 7. The Windows clients can see >all the other machines (including the older Samba server), so I am >assuming the Samba server is providing master browser services (and >log.nmb reports that it is the domain and local master browser). smb is >reporting no...

...ba.org/mailman/listinfo/samba>, <mailto:samba-request@lists.samba.org?subject=unsubscribe> List-Archive: http://lists.samba.org/pipermail/samba/ Three days into trying to install samba, I have gotten up to Test 7 in DIAGNOSIS.TXT, sort of. Test 5 says, run the command "nmblookup -B ACLIENT '*'" This always returns the ip address of my Linux box, no matter what I put for ACLIENT (even made up garbage), but if I substitute the actual IP for ACLIENT, then it works. test 6 says, Run the command "nmblookup -d 2 '*'" This works and shows me both the Linu...

...SW Jul08 0:00 [smbd] root 21990 0.0 1.2 1140 376 pts/1 D 20:07 0:00 fgrep 10422 [root@cesam /]# ----- Also, nmblookup works nicely: ----- [root@cesam /]# nmblookup -B CESAM __SAMBA__ querying __SAMBA__ on 192.168.0.3 192.168.0.3 __SAMBA__<00> [root@cesam /]# nmblookup -B ACLIENT '*' querying * on 0.0.0.0 192.168.0.3 *<00> ----- I've done everything in DIAGNOSIS.txt: everything related to smbd does not work, everything related to nmbd does work. The solutions provided in DIAGNOSIS.txt did not work. I've also search (quickly) the mailing list archive b...

...------------------------------------- #!/usr/bin/perl -w use strict; #*********** Start of Customization Area *************** my($BIGSERVER) = "pceurp52"; my($BIGSERVERIP) = "155.99.40.83"; my($TESTSHARE) = "//$BIGSERVER/TMP"; my($USERNAME) = "username"; my(@ACLIENTS) = ("RAM", "KERNOFFICE"); my(@ACLIENTIPS) = ("155.99.40.45","155.99.40.51"); # **************** end of customization area *********** my($LOGNAME)="diagnosis.log"; my($PASSWORD); sub writelog { system ("echo \'$_[0]\' >> $LOG...

...ed to my smb.conf file: security = domain workgroup = MYDOM encrypt passwords = yes password server = MYDOMPDC Created the smbpasswd file: cat /etc/passwd | mksmbpasswd.sh > /etc/samba/smbpasswd When running the diagnosis test, the following tests work: 1: testparm 2: ping BIGSERVER and ping ACLIENT 3: smbclient -L BIGSERVER lists the shares 4: nmblookup -B BIGSERVER __SAMBA__ returns BIGSERVER's IP 5: nmblookup -B ACLIENT '*' returns ACLIENT's IP 6: nmblookup -d 2 '*' returns a long list of NT boxes on the domain 7: smbclient //BIGSERVER/Public works for the one accoun...