To create themes and to answer in the forum be registered or take advantage of a guest login below. For viewing of the forum registration is not required.

Forum » Main » Main forum

Importing from AD

First | 1 | 2 |

Author	Message
Written on: 06. 03. 2008 [21:00]
Old forum user	Version 3.1.32.0 If I use the Authenticate through AD option Domain controller name srv.xxx.local Domain controller IP 10.10.1.2 Then the only thing I get is – login failed. Is it needed to store passwords in the AD database? Storing passwords in the text format is quite a severe violation of security rules. The user database was filled in properly, but the passwords were transformed into automatically generated numbers. What’s the correct way of setting up authentication through AD?
Written on: 06. 03. 2008 [21:00]
Old forum user	So you’re setting the same settings that you used to import data from OnLAN DBSync AD? This is strange... because the mechanism is almost identical... What’s your OS (version, language, sp)?
Written on: 06. 03. 2008 [21:01]
Old forum user	Server 2004 SP4, English. Domain controller, scheme 31 (there is a Server 2003 R2 domain controller in the domain).
Written on: 06. 03. 2008 [21:02]
Old forum user	Never had any problems with Server 2004, nor Server 2003 R2 either tbh. Scheme version is fine as well. You need to use e.g. Smith as login name on the client side, and not Smith(аt)srv.xxx[dot]local . It is imperative that you use Smith, because OnLAN Server will modify it appropriately. Put in the password from the AD database, and don’t mind the internal database. Does the OnLAN Server machine have any problems with physical connections (firewalls, routing issues, etc)? LDAP protocol (port 389) for AD is being used with encryption or without?
Written on: 06. 03. 2008 [21:02]
Old forum user	LDAP is being used without any encryption. I’m still unable to setup the authentication through AD, seems like we’ll have to use the internal database for the time being.
Written on: 06. 03. 2008 [21:03]
Old forum user	Strange... let’s try it like this: Domain controller name: xxx.local Domain controller IP: 10.10.1.2 Try to access the program through the client using the admin login name and its AD password (without xxx.local) Since you’ve updated the database (OnLAN DBSync AD), then there cannot possibly be any problems with authentication.
Written on: 06. 03. 2008 [21:04]
Old forum user	I’ve been away for a week – studying. Now I’m back, checked it and it works. You’re right; we need to put the domain name, not the domain controller name. Thanks for your help.
Written on: 06. 03. 2008 [21:05]
Old forum user	Hmm, new problem... Some clients can log in, see each other’s status (online/offline) and send messages, but the messages do not reach their destinations. They don’t appear in the server history either, and their status remains unchanged (unsent). The policy is set to default User. Which services does the OnLAN client use?
Written on: 06. 03. 2008 [21:06]
Old forum user	The error code is 300. P.S. Happy New Year!
Written on: 06. 03. 2008 [21:06]
Old forum user	Thank you, happy new year to you too! Can clients connect to each other physically? If they are in different networks (VPN etc), then you need to enable zoning. Go to User editor and set the zone codes. Each office (login name list) should have a separate zone code, doesn’t matter what the code is, as long as it is unique. Connection between zones is established through the server, and users in the same zone connect to each other directly. This leaves only one requirement: users in all zones must have a p2p connection with the main server. Since the main server is located in the headquarters, that gives us the classic star-like network scheme, which is easy to setup within VPN networks.

First | 1 | 2 |

Powered by mm_forum v0.1.7