similar to: Please help! Updated to Redhat 8.0, now can't get samba to work

I keep getting "Windows cannot copy file \\ssp1\profiles ... to C:\Documents And Settings\..." when trying to log into a Samba PDC using a Windows 2000 SP2 client. Does anybody have any ideas on how to fix this? I am including my smb.conf file, below: # Global parameters [global] workgroup = DC1 netbios name = SSP1 server string = Samba Server encrypt passwords = Yes update

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

http://bugzilla.mindrot.org/show_bug.cgi?id=1051 Summary: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Product: Portable OpenSSH Version: 4.1p1 Platform: ix86 URL: http://www.tietoenator.de OS/Version: Linux Status: NEW Severity: critical Priority: P4

It's really weird how many times thing break in threes. This time is was my wife's laptop, my router and a phone. Anyway... My network has a router and 2 computers; my F11 box with the samba server on it called steve and my wife's laptop now running Windows 7 called Kellie-PC. My old router was a Linksys WRT54G that I had flashed with DD-WRT. I was using DHCP and DNS masquerading in

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

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.

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

I'm debugging my Samba setup using the "Troubleshooting Techniques" from Sam's Teach Yourself Samba in 24 Hours. Everything works fine up until the nmbd section. I am able to do the following correctly: nmblookup -U 127.0.0.1 __SAMBA__ nmblookup -U 127.0.0.1 POGO (the server) nmblookup -B 192.168.1.255 WIN-CLIENT (the client) but when I do nmblookup -B 192.168.1.255

I've got Samba 2.2.2 installed and running fine on one of our servers (RS/6000 AIX 4.3.3 and using NT authentication), however, when I do Test #4 (from docs/textdocs/DIAGNOSIS.txt) it looks like this: npssrv{root}#nmblookup -B npssrv _SAMBA_ querying _SAMBA_ on 173.148.200.113 name_query failed to find name _SAMBA_ The test said I should get back the IP address of our samba server. I got

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

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.

> 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 =

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

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

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

Hi, here is a client computer and a server computer (Debian Wheezy, armel, samba Version 3.6.6, IP address: 192.168.1.2, Name: xyz). Problem: wins doesn't answer nmblookups by the client on the broadcast address: client$ nmblookup -S xyz querying xyz on 192.168.1.255 name_query failed to find name xyz Why is that so? How to fix this? When I specify the the server IP I do get an answer:

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

Hi, I would be very grateful if anyone could give me a bit of help with this. I am trying to run Samba 3.0.5, as distributed with Mac OS X server 10.3.8, on an Apple Xserve. Things were working beautifully until I had problems with an IP address change and had to reinstall everything. At present, the situation seems to be that the smb protocol is operating, since I can make an smb