FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Directory

 
 
LinkBack Thread Tools
 
Old 03-21-2011, 02:37 PM
Aaron Hagopian
 
Default Problems to access Directory Server from remote console with 389-console

Virtualbox networking can get a little goofy sometimes. *You may want to try a bridged network adapter instead of the default NAT.

On Sun, Mar 20, 2011 at 5:11 PM, Daniel Gonzalez <gonzalezdr@gmail.com> wrote:


Hi Guys,



My name is Daniel Gonzalez and I am new to this mailing list, I hope to

ayduar as I can while I'm learning a bit more about Directory Server 389.



I would also start with my first question.



I tested 389 on a Virtualbox virtual machine, I installed it



Fedora 14 (Minimal instalation)

389-ds



I followed the wizard to set 389-run setup-ds ds-admin.pl and all goes

well there



But when I try to connect from a console 389 on another machine I fail to



Am I doing something wrong? I need some configuration.



I turned off the iptables for this I'm not blocking ports or something

but still not working.



The good news is that if I worked in there too I have my machine I

installed fedora 14 389-ds and successfully run setup-ds-admin.pl to run

389-console and console to open it immediately login



I hope you can make me some suggestion.



--

389 users mailing list

389-users@lists.fedoraproject.org

https://admin.fedoraproject.org/mailman/listinfo/389-users



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 

Thread Tools




All times are GMT. The time now is 09:33 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org