similar to: smbclient sees my shares, but net view on Windows doesnt'

I have played around with samba now for quite a while but couldnt print on my win2k box with koffice. with the command line smbclient it works: smbclient //server/hpdeskje -N -P -U user -c 'print hello' prints a text (from the file hello) "Hello World" Also a print to file file off my win2k box would print fine with smbclient. Only, I cant quite find out how the printcap

Hello Again! I now have a virtual host serving (almost) samba and a real one serving samba under the original name. On the local machine, I can access the the virtual host through smbclient and smbmount. Everything seems all right. Unfortunately, the virtual host won't serve the windows-9x machines. The virtual (and real) host both appear on the network browse list but when the win clients

Hello everyone, I had been struggling with the issue, and eventually found the root cause. But I noted it's not mentioned here, or on the internet. Solution below, after the details. The symptoms are that on Windows 2000 you can C:\> net use X: \\server\share (maps the drive successfully) and C:\> net view \\server (lists the various services). But doing this: C:\> net

Hi, to whomever it may concern.i am a novice linux user using Redhat 8.0 on kernel 2.4. recently i installed samba 3.0 by compiling the sources and everything went on smoothly till installation completed successfully. but the samba doesnt start at all neither does the swat service.i did everything as it was adviced to do. * i compiled with options ==> --with-acl-support

I've seen variations on this problem in the past but they haven't seemed to help much in this instance. I have Samba running on a NetBSD(sparc) and would like to set it up to print to a Canon BJC-2100 running on a networked Windows ME machine. (My sparc box lacks a 'standard' parallel interface and I lack an adapter). I can print just fine to the printer from a second Windows

i'm running samba on solaris x86 only for accessing NT shares. samba is not running as a domain master or anything. the problem is that when i try to upload 18mb file to NT share, smbclient crashes. $ smbclient //<box 1>/<share A> added interface ip=x.x.1.30 bcast=x.x.255.255 nmask=255.255.0.0 Domain=[ACCORD] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] smb: \> put

I've installed Samba 2.2.3a on a Debian Linux machine and am trying to mount a file directory from an NT machine. When I use smbclient as in smbclient //etbodnyk/work -U fciam/bbodnyk it prompts me for a password and I can get to my work directory. When I try to mount the directory using mount -t smbfs -o username=fciam/bbodnyk //etbodnyk/work /mnt I again get prompted for a password but

I seem to be unable to view (smbclient -L) shares on a win2k machine. Directly connecting to a share works though ... Thomas --

Ok.. I've tried tweaking several settings on Samba (1.9.18p4) in order to try to keep it from killing several machines that get backed up weekly via Amanda (using smbclient). What always appears to happen is that for one reason or another, Samba is booking along copying files and then all of a sudden NT stops communication and smbclient ends up hanging forever (regardless of the keepalive

Hi list. I'm new to this list, so please bear with me. I've got samba 2.2.8a on Solaris 9 (SPARC). I've run all the tests. testparm runs fine. Other tests: # nmblookup -B stage __SAMBA__ querying __SAMBA__ on 192.168.18.25 192.168.18.25 __SAMBA__<00> # # nmblookup -B 192.168.1.9 '*' querying * on 192.168.1.9 192.168.1.9 *<00> # # nmblookup -d 2 '*'

Dear Samba Gurus, having a browsing problem with W2k (German Version) on my 2.0.9 server (also tried 2.0.7 before), you are my last hope to help me soling my problem! Everything is working fine accessing the samba server from linux, no problem at all, all shares are listet with exact namewith smbclient -L ixdp425 (Intel Xscale Developper Plattform ixp425 Proz.) I'm also able to "net

Hi Guys I am using samba-3.0.10 and Redhat Enterprise 4 on a linux machine called "c4dev". I have this share on my XP machine called "Spare110-lt" setup with access to "Everyone" and had Guest account enabled. Windows XP IP address : 192.168.1.68 Samba server address : 192.168.1.65 Both machines are in the same workgroup called "IOKO365". When I try to

List, while trying to list all shares in my network using smbclient I recognized that some shares are missing. ("hostname" is a Win2K Box). smbclient -L -U "" -N hostname shows no shares (using NULL-Session-Logon as you can see) if I use a windows box to connect to "hostname" using net use \\hostname "" /User:"" I can see all shares of this

Hi folks, From my RedHat Linux box Im using smbclient L to obtain the list of shares on a particular computer in the network. I use guest as user name or just omit the user name. I can get the list of shares on every single Linux or Win9X machines in the network but I cannot obtain the list of shares on Win2000 and Win NT machines. Here is what I tried: [user1@linuxbox user1]$ smbclient

On 06/03/15 20:30, Al Schapira wrote: > Marc, et al, > > Thanks for your reply. Sorry, I didn't mean to be confusing. > > Summary of problem: > 1) XP sees samba shares on fedora14/samba3 machine, but not on > fedora20/samba4 machines. > 2) all fedora machines see all shares including on XP machine. > 3) clicking on f20 machine from XP tries to log in rather

Hi, isn't it possible, that your new Samba4 server uses higher SMB protocol, than the old MS windows XP machine can understand/handle? Not sure about this, but might be worth checking? cheers :] -- *Karel Lang* *Unix/Linux Administration* lang at afd.cz | +420 731 13 40 40 AUFEER DESIGN, s.r.o. | www.aufeerdesign.cz On 03/06/2015 02:42 AM, Al Schapira wrote: > Hello, > > A

Hello Al, Am 06.03.2015 um 02:42 schrieb Al Schapira: > A windows XP machine 'X' (the only one left in the LAN) sees all > fedora14/samba3 shares on f14 machine 'A' but cannot see fedora20/samba4 > shares on machines 'B' or 'C'. > > 'X' can ping all of the others by name, and all of the others 'A', 'B' > and 'C'

Hi, I use Samba 2.07 as shipped with Debian 2.2. I have two computers connected in a network, a WinNT 4 SP3 box and the Debian box. With my previous setup (Debian 2.1, Samba 1.9?) it was a snap to share the home directories and the printer on the Debian box. After upgrading, things changed a bit: - I can still connect from my NT account to my home dir on the Debian box with the same account

I have just recently installed Samba. I have two WinXP Pro machines networked to a FreeBSD 5.4 computer. The Printer is connected to one of the WinXP machines currently. This is the output of the 'smbclient' command. smbclient -U user-name -L winxp Password: Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment ---------

On Fri, 2015-03-06 at 21:59 +0000, Rowland Penny wrote: > try adding 'map to guest = Bad User' to smb.conf > > Rowland > IT WORKED!!! THANK YOU. Now the XP machine can see both the f14 and f20 shares. (It was not even necessary to restart nmbd or smbd on the f20 machines.) Now, if I'm not asking for too much, can you please explain why this worked. :-) Many thanks