similar to: Mac OS X + Samba + NT = Snag

I am running a sparc 20 with Solaris 2.5.1. I am trying to attach 95 an NT4 machines to it. I got the compiled Samba off the net somewhere and did a pkgadd. It installed fine. I have read the man pages and the FAQ, and run the tests on the UNIX side and all are fine. FYI, these are: smbclient -L nmblookup -B (on server and client) nmblookup -d 2 '*' nmbclient '\\av\tmp' (av is

Hello all. I've decided to try using samba on our Solaris systems to give users who are stuck with PCs on their desks access to our gis data. I obtained a compiled binary package of version 2.0.7 from one of the samba.org sites, and have installed SAMBAroot, SAMBAusr, SAMBAman, and SAMBAdoc. All apparently worked just fine. I've made a couple of changes to the smb.conf file, changing

I am having a hard time getting samba 2.0.4b running on a Sparc20 running Solaris 2.5.1. I have swat and smbd running, but not nmbd. I have tried all the stuff in diagnostics.txt and have searched the archives but am still stuck. I have tried to gather some useful info, in the hopes that some on this list will be able to figure this out. Thanks in advance. Here are the results of some of the

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 '*'

I'm hitting a snag with htaccess. Have created .htaccess and .htpasswd files, set up apache directory options just like always... the exact same setup works fine on CentOS 3, but I can't seem to get it to authenticate on CentOS 4? Am I just being blind stupid (as in not seeing something 'exactly the same') or is there something different I'm missing? I have selinux running

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

I spent most of the evening trying to boot a new install of CentOS in a VirtualBox VM. The VM recognizes the install DVD, runs it, asks for me to boot it and I type in <return> (or any number of other combinations, all of which fail in exactly the same way) and it continues to run up to the point shown in the attached screenshot. I've tried numerous different combinations of device

Hi Lee, > let isReturn = 1, isTerminator = 1, isBarrier = 1 in > { > def RET : BitscuitInst<(outs),(ins),"JMP\tR6",[(Bitscuit_return)]>; > > def JMP : BitscuitInst<(outs), (ins jmptarget:$dst),"JMP\t$dst",[(br > bb:$dst)]>; > } Ah! It looks like the isReturn is to blame then. LLVM is presumably going through adding an implicit use of any

Hi Lee, > Massive thanks, I've been staring at this problem for so long I was beginning to go a little stir crazy. No worries. I know how annoying it can be trying to fix these problems. "isBarrier" is the one that usually got me. > Out of interest is there a good explanation of the various isterminator etc flags anywhere? The best I know of is

I'm trying to troubleshoot a new samba setup on a tiny network, and I'm clearly missing something. I'm running Samba 3.0.22 on Ubuntu Linux. When I first set it up, it seemed to go so smoothly. I changed all the workstations to the same workgroup (RABNETWORK) and they could see each other and the server, but they couldn't open anything on the server. I don't really understand

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

Environment: AIX 5.2 Samba 3.0.21b (compiled at this site with Visualage C/C++ 6.0) configure was run as: ./configure --prefix=/usr/local/samba --with-pam --with-acl-support --with-aio-support --with-winbind Windows environment is a mix of Windows NT domain and Novell file servers. Does anybody know of a single document or set of documents that have a "cookbook"

This is getting real tough to debug. titan : Solaris 8 running samba 3.0.31 aequitas : OpenSolaris running samba 3.2.0 I can do basics test just fine : # /usr/xpg4/bin/date -u;/opt/csw/bin/findsmb Sat Jul 12 22:50:51 GMT 2008 *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION

Samba not responding to broadcast calls from networked PCs. Short: My Redhat Linux 8.0 box is not replying to udp broadcasts, and I can't figure out why. Network: The offending Redhat 8.0 Linux Box (//DS) attempting to run Samba 2.2.7 Firewall Redhat 7.3 (//IW) successfully running Samba 2.2.4 Win98 (//MS) Win2k (//SL) <Not running at the time of these tests> Very long: I've

Hi All, Due to a hard-disc crash, I have just upgraded from a working Samba setup running in FC2 to a non-functional Samba setup running in FC3. The Windows XP machine has not changed, but won't connect. Samba is fully up2date from the FC3 repositories. smb.conf [global] workgroup = MYGROUP server string = Samba Server hosts deny = ALL hosts allow = 192.168.1.0/24 127.

Troubleshooting steps fail. Trying to replace a standalone Netware server with a Samba4 server with AD. To isolate this test setup, changed server's static IP address and separated the wiring. Then went through the Troubleshooting portion of The Samba Checklist. Some tests pass. Some tests fail. I'm weak on Samba, DNS and AD. I appreciate your instructions on how to overcome the

> Maybe there isn't a glibc version (although > it shouldn't be hard to port the Solaris version to >glibc). I will try to port nss_wins to glibc. I made some changes to smb.conf and follow the tests described in Samba diagnosis (www.samba.org/samba/docs/diagnosis.html) smb.conf [global] workgroup = NETMANAGER server string = Deltacom Samba Server printcap name =

I used to be able to browse the windows shares on the network through Nautilus. I can see them as computers, but when I click on them, it fails. (I'm on Ubuntu 6 LTS, AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am

I make all steps in the guide: http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#id2546028 but command (exetuded in the same computer where is samba): smbclient //fc9/tester -Utester%test gives error: Domain=[DZTI] OS=[Unix] Server=[Samba 3.2.0-17.fc9] tree connect failed: NT_STATUS_BAD_NETWORK_NAME The user tester have been created by commands: useradd tester smbpasswd -a

I'm having a perplexing problem with a multiple configuration setup. My setup was working fine until I changed the IP address of my server. Since then, Samba has been misbehaving. All other networking processes are working fine so I don't believe it to be a o/s issue on the system. The system is running Solaris 2.6 using Samba 2.0. My client and the server are on the same TCP/IP class, a