similar to: can connect to 2 samba servers by name but to one by IP only

> > > Adding pdc1 to the hosts file (c:\windows\system32\drivers\etc\hosts) > did > not make a difference. After adding pdc1 to lmhosts, "net use > \\pdc1" did > work. So in the case of pdc1 one, the name is being resolved as a > netbios > name (i.e. via lmhosts) not a tcp/ip type name (i.e. via dns or hosts) > > But then why does "net

On Wed, 21 Jun 2017 11:55:47 -0400 Gaiseric Vandal via samba <samba at lists.samba.org> wrote: > I increased the logging to 10 on the problem member server. Didn't > see anything of interest. > > I did a packet capture on the PDC while typing " net rpc testjoin" > from both the problem member server (4.4.14) and a working member > server (4.4.13) > >

Setting my domain controllers to use SMB2 breaks windows domain authentication for Windows clients. I don't know why. The clients in question are Windows 7 and Windows 2008 R2. Once I set the domain controllers and problem member server to server max protocol = NT1 server min protocol = NT1 client max protocol = NT1 client min protocol = NT1 the

I increased the logging to 10 on the problem member server. Didn't see anything of interest. I did a packet capture on the PDC while typing " net rpc testjoin" from both the problem member server (4.4.14) and a working member server (4.4.13) e.g SMB: ----- SMB Header ----- SMB: SMB: CLIENT REQUEST SMB: Command code = 0x72 SMB:

Samba is causing a couple huge problems for the NT admins here since we switched a bunch of machines to security=server and started running nmbd. We're running Samba 2.0.2 and 2.0.3 on a mix of Solaris, HP-UX, and OSF1 machines. One, selecting a Samba server in Server Manager, then selecting Computer/ Services causes Server Manager to crash ("An application error has occurred, blah blah,

Good catch. I had set server max protocol to NT1 after upgrading from samba 3.x to 4.x . Some windows clients had problems with SMB2 and file shares (tho this should not really be an issue with the domain controllers.) I have now set the dc's to server max protocol = SMB2 server min protocol = NT1 and the client machine to be client max protocol = SMB2

There may be various "signing" parameters that you may need to set to "no"  on the samba PDC. I would also disable SMB3.   Windows 10 does support SMB3 but (in my experience) Samba does not properly implement it, so you will get problems.  Windows 7 does not support SMB3 so will fall back to SMB2 anyway. I suspect at this point making Windows 7 and Windows 3.11 interact

We have the situation where we are trying to send to a server that has a cluster configuration. When we negotiate, it tells us to talk 3.11. When we actually try to send the file, the share's max protocol is actually only 3.02 and so the Microsoft server sends a NT_STATUS_SMB_BAD_CLUSTER_DIALECT, which means they expect the client to reconnect negotiating only 3.02 as max protocol. Looking

I am currently using samba 2.3a-12.3 as a PDC, here is my smb.conf [global] netbios name = kidpaddle workgroup = JUDO domain master = yes local master = yes preferred master = yes os level = 255 wins support = yes time server = yes security = user encrypt passwords = yes domain logons = yes domain admin group = root davidj logon drive = H: logon

Hello. I need to let Windows for Workgroup 3.11 clients (industrial machinery) connect to shares in the PDC samba Version 4.2.14-Debian. I started to be able to connect to shares exported by domain members windows professional (7, 10) machines (share permissions include "domain users"), after I added "lanman auth = yes" to PDC and updated the user password, though it's

I have a samba domain with a Samba 3.4.x PDC (compiled from source on Solaris 10) and two Samba 3.0.x BDC's (Sun-bundled Samba on Solaris 10.) XP clients use DHCP. When on the LAN, DHCP includes WINS server (the WINS server is one of the Samba 3.0.x machines.) We also have a VPN for remote client access for Windows XP machines. XP machines could include home PC's (not in the domain)

Hi! After more work on the oplock_break problem, I've found the following in my tcpdump-smb logging. It seems that when ost5 (pid=26339 in the logs that follow) requests access to the oplocked file comm.inf from ost6 (pid=5872) the oplock_break failes (this is NOT isolated to any one or two systems on our network, just using these two as an example, and the server reports no dropped packets

While trying to switch a domain from an WinNT 4.0 SP ? to an AIX 4.3 with samba 2.2.8 with OS2/warp 4 clients we receive some unexpected errors. - we can log on to the new domain , run logon scripts, map network drives , store and retrive files , print to a Remote server using the printers shared by samba. - we can't run VisualAge Generator (2.X) retriving files from the samba server. (we

Hello list, The issue is as the topic says, following are details: the Samba server running as ADS member, NBT enabled on Windows machines, no WINS. Windows machines can find each other by 'nbtstat -a' but cannot find the Samba server. The Samba server can't find neither Windows machines nor itself by 'nmblookup -a <netbios-name>', error message is "could not open

Hi all, I have found this: time smbclient -L //debian -U% Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers software Disk IPC$ IPC IPC Service (Samba 4.7.7-Debian) HP_F4100 Printer HP Deskjet F4100 series MX870-series Printer Canon MX870 series l6p Printer l6p MX435

Problem: -------- On the client mascines I get the msg: "The account is not authorized to log in from this station." This has bugged me for days now, so I am posting this sloution around varius places on the net... Analysis: --------- from a round of analysis by Jamz Boman B.Sc (Jamz@Boman.com), Toby Corkindale (tjcorkin@steadycom.com.au) Andreja Zivkovic (zivkotech@ozemail.com.au) at

Hi! Been having the same problem with oplocks for a while and have been trying to figure out what's going wrong. The FAQ says that we may have a networking (hardware?) problem, but according to the Linux box's ifconfig results, we have had no errors and no dropped packets on the internal network. I am able to reproduce the error pretty much at will on our network, and it is not isolated

Hello, I'm using LDAP as my passdb backend and I am having a problem joining my machines to the domain. I am running Samba 3.0.10: When I run: [root@core1 samba]# bin/net rpc join -U Administrator%5P4nkm3 Create of workstation account failed Unable to join domain VOIP. >From the command line, this is what appears in my smbd logs: [2005/01/27 17:14:44, 0]

Hey All, RedHat 9.0 samba-3.0.10-1* * I was attempting to allow several domain users the ability to log into my domain controller with their logins. Because the server had no local group set up for the users, I created them with the groupadd utility. About 10 minutes later I got a call from my users telling me they couldn't access their network shares because the drives hadn't been

Greetings! I have the following configuration: Two PDCs with Fedora Core 4: PDC1 and PDC2. PDC1 trusts PDC2, respectively PDC2 is trusted to PDC1. I join an XP workstation to PDC2. After restart i can see both domains in the login screen domain combo box. I can logon to PDC2 , but not to PDC1, since the PDC2's /etc/passwd