Displaying 20 results from an estimated 30000 matches similar to: "XP joining domain - problem"
2003 Nov 03
1
FW: XP joining domain - problem
-----Original Message-----
From: Mike [mailto:vje@adelphia.net]
Sent: Monday, November 03, 2003 1:23 AM
To: rruegner
Subject: RE: [Samba] XP joining domain - problem
Hi,
Thanks for the quick reply. Here are the smbd and nmbd logs. I'm not sure
if you need the nmbd, but I wanted to include it just in case. Sorry I did
not include them in the initial email.
Sincerely,
Mike
====START OF
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi Peris,
> some years ago i configured a `Primary Domain Controller` through
> Samba and LDAP (slapd) on an Ubuntu machine (13.10) at 192.168.69.203
> which should be accessible by the string/name `SRV1`. I must note i
> did not installed winbind. I've never had any issue and it looks like
> it's working fine as about 10 Windows machines joined the PDC and
> Windows
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi,
i've tried adding server max protocol = NT1 into /etc/samba/smb.conf
and restarting smbd and nmbd services but it didn't do the trick.
I feel like Windows clients are not able to resolve SRV1 into the PDC
and so they can't event try to join the domain.
On Fri, May 20, 2016 at 4:22 PM, Pau Peris <pau at webeloping.es> wrote:
> Hi,
>
> thanks a lot for the tips. I
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
I'm completely lost as i can ping SRV1 without issues but i'm starting
to think that maybe Windows tries to join the domain through IPV6.
ping -c6 SRV1 from this Windows 10 machine leads to host not found so
i'm working on this direction right now.
Any help will be really appreciated
On Fri, May 20, 2016 at 5:04 PM, Gaiseric Vandal
<gaiseric.vandal at gmail.com> wrote:
> I
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
Right now i'm out of the office and i have no way to remotely work
with the Windows machines so i've been upgrading the server to Ubuntu
16.04. Everything seems to be working as before but i'm wondering why
right now the Master value is blank for Workgroup exedra.cat Any idea?
# smbclient -L localhost
WARNING: The "syslog" option is deprecated
Enter root's password:
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
Are you running a wins server (maybe you already mentioned this.) That
tends to help minimize some classic samba issues.
On my PDC
root at mypdc:~# testparm -v | more
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (256) to minimum Windows limit
(16384)
Processing section "[netlogon]"
WARNING: The
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi,
thanks a lot for the tips. I already did the first one, importing the
following into the registry:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
"DomainCompatibilityMode"=dword:00000001
"DNSNameResolutionRequired"=dword:00000000
I didn't do the second tip but it looks like it's not
2016 May 20
3
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi all,
some years ago i configured a `Primary Domain Controller` through
Samba and LDAP (slapd) on an Ubuntu machine (13.10) at 192.168.69.203
which should be accessible by the string/name `SRV1`. I must note i
did not installed winbind. I've never had any issue and it looks like
it's working fine as about 10 Windows machines joined the PDC and
Windows users can login against PDC on
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
I was trying to fix a problem on Windows 10 with Outlook 2013. Also
running an NT4-style domain. The machine had already been joined to
the domain and outlook had been working but recently not (probably after
patch tuesday.) I also had had problems with Win 10 mail and RDP.
I came across the following link.
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
You should be able to unbind ipv6 for the win 10 machine's network
interface.
does "nslookup SRV1" work?
Also, you may want to try running tcpdump or ethereal or wireshark on
our PDC and see what traffic is captres.
On 05/20/16 13:24, Pau Peris wrote:
> I'm completely lost as i can ping SRV1 without issues but i'm starting
> to think that maybe Windows tries to
2004 Apr 05
0
"DNS name does not exist" when joining Samba PDC domain
I am attempting to join a domain managed by a Samba PDC from several
Windows machines, both Windows 2000 Professional and Windows XP
Professional. They all give a similar error. The Windows 2000 error
gives me a URL that redirects to:
http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp
The XP error is attached.
Any idea how I can fix this problem? If necessary, I can modify the
2004 Nov 18
0
Difficulty joining domain
I'm trying to get an LDAP PDC running, and when I try to join a
Windows computer to the domain, I get the following error:
"The specified domain either does not exist or could not be contacted"
That's from Win2K. WinXP gives more information:
-------------------------------------------
The domain name NWU_FLUFFY might be a NetBIOS domain name. If this is
the case, verify
2016 May 20
1
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi,
thanks a lot for your reply.
Yes, i enabled wins through "wins support = yes", i also enabled
lmhosts lookup and wins on all clients but will check it as you
proposed. Tomorrow will try to disable ipv6 on Windows clients
following this link https://support.microsoft.com/en-us/kb/929852
Which process did you follow to disable IPV6? I'm also wondering if
it's really necessary
2005 Aug 14
1
Samba server with Win XP clients: Problems.
Hello!!
I am trying to set up a Samba server with Win XP Pro
clients.
In brief, this is the current set up:
Comp1: Firewall (DHCP) Linux
Comp2: Proxy (Squid) Linux
Comp3: W2K server (AD)
My final objective is to replace Comp3 with a Linux
server (Fedora Core 3) running Samba, which in turn
will handle the roaming profiles.
This is current problem that I am encountering:
I edited the smb.conf
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
Excuse me for the little flood please, i've just checked it again and
now i see SRV1 as master for exedra.cat workgroup, i event can see in
the logs Samba name server SRV1 is now a local master browser for
workgroup EXEDRA.CAT on subnet 192.168.69.203
So i'll keep digging on how to fix the issue exposed on my first
email, tomorrow i'll try to see wether it's an IPV6 issue or
2003 Oct 20
2
Samba 3.0.0 PDC, XP SP1, and domain joining woes.
Greetings, you kind and wonderful people.
I've spent the past few hours or so (read: all day) attempting to get a basic
PDC up and running, with no success.
I've even gone to the extent of copying John Herpstra's config, which contains
all sorts of weird and wonderful stuff, in the hope that he had something I
missed. He didn't.
I've got one box running debian testing, with
2007 Jul 13
1
DNS-error from one machine when trying to join domain
Hello again.
I finally managed to setup samba as a PDC and I was delighted to see that it
actually worked this time, thanks to a few people here on the list. I could
join the domain from the a computer running XP but I'm having some trouble
when I try to connect from another computer. I get the following message;
"A domain controller for the domain could not be contacted
The error was:
2006 Oct 12
0
issues adding XP clients to domain
Hi Group,
I have a nasty problem keeping me busy for some time now, I have a
samba3 server on Solaris10 who has worked for several years with win98
clients. Now we want to migrate to XP and the domain part is giving me
trouble.
I am rather new to windows XP and domaining so be patient with me please.
My smb.con looks like this :
# Samba config file created using SWAT
# from 192.168.10.10
2004 Jan 16
2
Samba 3.0 pdc and winxp
Hi,
I am trying to get an xp machine to join a samba 3.0 pdc domain.
I keep getting the following error below. I can view the pdc shares with
no problem. Can anyone point me in the correct direction on getting this
fixed. Any help would be greatly appreciated.
The domain name homenet might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with
2023 Dec 15
1
Joining Windows 10 Domain Member to Samba AD/DC
On Thu Dec 14 19:27:29 2023 Matt Savin <matt at tegers.com> wrote:
>
> Hello Mark,
>
> When joining the domain, did you specify domain name as hprs.locl, or hprs
> only? Please try to specify hprs.locl.
>
> BR,
> Matt
Matt - yes I did specify hprs.locl. I just tried it again and it failed again.
This time I opened the "Detail" box which says: