similar to: NT 4.0 problem

I support some organizations using Microsoft Small Business Server 2000, with relatively simple Active Directory domains. AFAICT, they use simple printer and server file shares for Windows 9x and 2K and XP clients, the centralized user accounts with server-mapped home directories, and not many other features of a domain. I want to plan a migration away from Microsoft Domain Controllers ASAP.

I have Samba 1.9.17p2 and it works great on NT4.0 SP2 When I update to NT4.0SP3, my Samba connection gives me the following message: The account is not authorized to login from this station. Did something change? Maybe NT4.0 SP3 uses a smb.conf option that wasn't used before? I've installed the package version from the Solaris 2.5 web site. I'm actually running Solaris 2.5.1

I'm running Samba 3.0.9 on SLES9 as a domain member with an NT4 PDC, using winbind to authorise domain users. I have set up a general share for all users which works fine and is accessible by all users but I am unable to set up the home shares correctly. When attempting to connect via smbclient I get the following:- tree connect failed: NT_STATUS_ACCESS_DENIED What does this mean and where

Thanks to Will Saxon I'm finally able to mount Samba shares on my 5.1-R box using the command mount_smbfs -I 129.197.36.34 -W acct01 //bfosdick@129.197.36.34/net-11 /sp/net-11 which then prompts me for my password. So now the question is...how do I put this in /etc/fstab? What do I do about the password?

Greetings, We are currently experiencing logon problems with a trusted domain user(s). Example: We have DomainA and DomainB DomainA and DomainB both have workstations joined on their respective domain. DomainA and DomainB both have trust relationships. DomainA trusts DomainB and vise versa. DomainA is where being served by a Samba PDC, while DomainB has a PDC using Windows NT 4.0 Server When

I have Samba Version 3.5.8-74.fc13 (Fedora 13) set up as the PDC for an NT domain. I have several Windows XP Pro and Windows 7 Ultimate workstations as domain members and everything is working fine. Domain users can log-in at the workstations, access shares on the Samba server and the other workstations, etc. I am in the process of adding Samba Version 3.5.8-76.fc14 (Fedora 14) as an additional

Hey, I have a problem with the integration of Samba 2.2.6 into a NT 4.0 Domain. My environment: - Samba 2.2.6 as SuSE rpm from samba.org - SuSE 7.3 Intel - Kernel 2.4.10 - running smbd, nmbd, winbind - NT 4.0 PDC (german edition) - NT 4.0- / W2K- / XP-client (german edition) - Joining the Samba into the domain looks like o.k.: + samba is in the browser list visible + wbinfo, getent show the

when using an nt 4.0 client, i can get non-guest access to all shares as i want. however, i cannot get access to any printers unless the printer is setup as a guest printer. nt 4.0 always seems to try to use the printer as guest user. nt 4 never gives me the chance to give a passwd for access to the server. (i do have SP3 on nt). if i use win 95 client, i can get access to all shares and

Hello, I want with the command : linux:~ # net rpc join -S DEMONT01 -w DOMNT -U Administrator%passwd migration from windows nt 4.0 to Samba 3 but i get always this : linux:~ # net rpc join -S demont01 -w domnt -U samba3%passwd Unable to find a suitable server Unable to find a suitable server linux:~ # what can i do? I have a bdc acount on the windows nt 4.0 for the samba 3 server.. With

Hi all, while fiddling with VmWare View without being able to join windows7 client to samba4 domain, we stumbled on the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028164 which says, should we run MS Windows 2008R2 AD, we should enable the "Allow cryptography algorithms compatible with Windows NT 4.0"

Hello, Can anyone advise if there is a limit on the length of share names in Samba when accessing via NT Workstation 4.0 clients? It seems that the limit is 12 characters for NT, our Windows 98, 2000 and XP machines work with longer share names. If so does anyone know if there is a patch to make long share names work with NTWS 4.0? Best regards, Keith

On Mon, Dec 5, 2016 at 12:02 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 5 December 2016 at 19:56, Hans Wennborg <hans at chromium.org> wrote: >> I'd like to avoid 4.1 because of the potential for confusion about >> whether it's a major release (as it would have been under the old >> scheme) or a patch release. > > But if the versioning

I am getting a complaint that my Samba server running on Solaris 2.5 cannot be found from a user's PC running NT Workstation 4.0. Any suggestions? thanks, garrett curtis garrettc@eos.net

Ever since I upgraded from Samba 1.9.18 to 2.0.0, I've been having problems with applications started from a Samba share dying silently, or with an Illegal Instruction message, on NT 4.0 Workstation. Since the only configuration change has been the Samba upgrade, that would seem to be the orgin of the problem. Below is my smb.conf file, in case I have something configured (or not configured)

Hi I believe that whole question is in topic. Is there any way to recognize ( and then shape ) p2p traffic which is encrypted? Modern p2p clients have this ability moreover some of them have this enabled by default. Now I''m using ipp2p for iptables but as I know this doesn''t recognize encrypted traffic. Thanks in advance. Pozdrawiam Szymon Turkiewicz

Hi, OpenSSH 5.2 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This is primarily a bug-fix release, to follow the feature-focused 5.1 release. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable

I am in the process of researching and testing SAMBA as a PDC. The only thing I am uncertain about is that our billing scheduling system is running WINS and our 110 pc's are configured to use it for wins resolution. I would like to leave WINS on that system but can it coexist with a SAMBA server acting as PDC but not doing WINS? I will be replacing an NT 4.0 PDC which has operated with

I have a server Unix with Samba version 2.0.6 and a server NT version 4.0, they are connected on a unique domain. The share directories are in the Unix server and the users - the groups (global and local) are in the NT Server. I don't kwnow how is it possible to give access to the shared folders on the Unix server with the groups defined on the NT server ? Please help me.

HI, we had a server crash and luckily no backup. So our samba domain is gone, so I had to set up a new server with a new domain. Except for one NT 4.0 Server all XP clients where able to join this new domain. When trying to put NT4 into the domain I get following error: make_connection: refusing to connect with no session setup. What changes in samba could be the reason for this message? This NT

Is the following developed in my console output a recognized bug or am I using the cat function incorrectly? Thanks, Stan > ifelse(class(data[[n]])!="factor",{print("yes")},{print("no")}) [1] "yes" [1] "yes" > ifelse(class(data[[n]])!="factor",{cat("yes")},{cat("no")}) yesError in ans[test & !nas] <-