search for: requiressignorseal

...res R/W. All I get is: /usr/local/samba/bin/smbclient //paulxp/"My Documents" passwd -Tc mydocumentsxp.tar Added interface ip=161.217.10.13 bcast=161.217.10.255 nmask=255.255.255.0 session request to PAULXP failed session request to *SMBSERVER failed I tried the regeditor to change the requiressignorseal to 0 and it worked just one time, now it's back to saying Sesssion Failed. -------------- next part -------------- HTML attachment scrubbed and removed

Hello Everyone, I have a question about what I need to know to configure windows XP to work with a samba share? Are there any resources out now that explain how to configure samba and XP to work together? Thanks for the information, Carey Hall -------------- next part -------------- HTML attachment scrubbed and removed

I upgraded to 2.2.2 on Solaris 7, and changed the regestry requiressignorseal to 0. Although this new XP is able to do the samba mounts I need, I'd like to be able to back it to UNIX tapes with smbclient, but all I get is : /usr/local/samba/bin/smbclient -L //paulxp added interface ip=161.217.10.13 bcast=161.217.10.255 nmask=255.255.255.0 session request to PAULXP fa...

...__________________________________________________ -----Urspr?ngliche Nachricht----- Von: John H Terpstra [mailto:jht@samba.org] Gesendet: Donnerstag, 10. April 2003 21:46 An: Michael Roark Cc: samba@lists.samba.org Betreff: Re: [Samba] Samba 2.2.7a and XP pro Michael, Did you apply the "RequiresSignOrSeal" registry change on the XP client? It is in the samba sources under ~/docs/Registry/WinXP_SignOrSeal.reg So in summary: Things to check: 1. In smb.conf [globals] encrypted passwords = Yes security = user 2. Make sure you have create the machine account: Logged in as root: useradd -d /d...

...o.za> > Sent: Tuesday, September 10, 2002 4:24 PM > Subject: RE: [Samba] Problem joing a W2KSP1 client to a Samba PDC (2.2.5). > > > > What is the sign or seal patch, is it updating the > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\netlogon\parameters > > RequiresSignOrSeal. Cause in W2KSP1 it already was set to 0, I tried with > 1 > > but that din't work either. > > > > /Tommy > > > > > -----Original Message----- > > > From: Trevor Fraser [mailto:trevor@systematic.co.za] > > > Sent: den 10 september 2002 15:21...

...that all mappings are automatically accessible once the machine is booted without the need to force the issue via Explorer ? Any help you can offer would be fantastic. Kind regards, Darren Stanton. Unix Systems Administrator. Santos Ltd. PS. We have tried (rightly or wrongly) applying the "RequiresSignOrSeal" reg fix found on the Web - No change in behavior. Santos Ltd A.B.N. 80 007 550 923 Disclaimer: The information contained in this email is intended only for the use of the person(s) to whom it is addressed and may be confidential or contain privileged information. If you are not the intended...

Hi, I'am running a small samba server at work with 10+ users in the domain (all of them added with W2KSP1 and 2.2.3 or 2.2.4). I uppgraded to 2.2.5 a while back and has not experienced any problem with it, but when I try to add a newly installed W2KSP1 client to the domain I get the following entries in the log file: Sep 10 13:29:55 linus smbd[17681]: [2002/09/10 13:29:55, 0]

I have read over the lists and search the web, I know this question has been asked before, but I've not been able to fix my problem so I'll ask here. I have been successful in joining the XP machine to the domain however it when I try to login to the domain windows instantly kicks up the message: "Windows cannot connect to the domain, either because the domaincontroller is down or

John, thanks for that hint. It did not kill the server by you are perfectly right. I changed this and restarted the "smb" and "nmb" deamons - unfortunately with the same result. When I watch e.g. the status with "swat" I see as follows after trying with: smbclient -U <user> -L win2k1 (what is strange since I connect as different user and not

Good evening all, I'm running samba 2.2.2a on RedHat 7.2 as a PDC and until today all was well. One of my users upgraded their workstation to Windows Xp pro and although they received a message "Welcome to the domain" when they try to log on they receive the message that the domain comptroller cannot be located to validate their account. The workstation show up in the browse list.