Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Server
User Name
Linux - Server This forum is for the discussion of Linux Software used in a server related context.


  Search this Thread
Old 08-09-2012, 07:40 AM   #1
Registered: Jul 2004
Location: UAE
Distribution: RedHat
Posts: 93

Rep: Reputation: 15
Unable to connect to 389 DS through Windows console

I've setup 389 Directory Server (1.2.*) in CentOS 6.3. I'm able to login successfully from within DS and do all the Administration tasks.But when I try to login to DS from a windows system using windows console provided by 389 DS , I'm unable to login. IPtables is in off state,SELinux is Disabled.Windows client is able to ping to the server,DNS entries are in place and I'm able to telnet to ports 389,9830 on server from windows. I've no clue. Please help.I'm attaching a screenshot of the error message I get when I try to login.
Attached Thumbnails
Click image for larger version

Name:	389_error.jpg
Views:	94
Size:	52.3 KB
ID:	10316  
Old 08-09-2012, 07:55 PM   #2
Senior Member
Registered: Aug 2009
Posts: 3,790

Rep: Reputation: 653Reputation: 653Reputation: 653Reputation: 653Reputation: 653Reputation: 653
I've never tried the windows version of the console so I can't really comment, but as a work-around you could just tunnel X11 to your pc and run the console on the server like I do.
Old 08-10-2012, 04:00 AM   #3
Registered: Jul 2004
Location: UAE
Distribution: RedHat
Posts: 93

Original Poster
Rep: Reputation: 15
Appreciate your reply. As of now I'm using windows Remote Desktop to do the configuration. But somehow I wanted this windows console to work.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
389 directory server - client unable to login. chengli Linux - Server 4 01-19-2017 01:52 AM
[SOLVED] bacula BCONSOLE PROBLEM: console JobId 0: Fatal error: bsock.c:129 Unable to connect Skullsoldier Linux - Server 20 12-01-2010 09:23 PM
Unable to access 389-DS Server through remote LDAP Admin tool? your_shadow03 Linux - Newbie 2 01-09-2010 03:17 PM
Unable to connect to Cisco devices via console/USB cable Nevski Linux - Wireless Networking 5 08-30-2007 02:22 PM
Unable to connect to cisco console with minicom nleachma Linux - Newbie 1 10-18-2003 10:22 PM > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 07:34 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration