[389-users] Problems with running Management and Directory Consoles on remote servers
Rich Megginson
rmeggins at redhat.com
Tue Jul 13 13:43:02 UTC 2010
Gerrard Geldenhuis wrote:
>> Yes, we were connected over a VPN as well - Cisco, in this case - with
>> the underlying networks being 100mbit LAN -> ADSL -> Internet ->
>> Datacentre -> 1000mbit LAN.
>>
>> Just now, as a test, i installed and ran Wireshark (gnome) via ssh -X to
>> the remote site, and from the same machine that i would normally have
>> run 389-console from. It was relatively responsive - certainly usable,
>> in any case.
>>
>> Could it be a java thing, or is it specific to the console tool, i wonder ?
>>
>>
>
> It's probably both... we have much the same network setup. The other setup being 100Mb -> vpn -> ADSL -> 1000Mb network.
>
> We will raise a bugzilla. I will send the number so you can add any additional info or just confirm another occurence of the problem.
>
This has been a problem for years - I believe it is a java thing - there
are unfortunately very few standalone java apps like the console with
which to confirm - there's really nothing in the console code itself
that controls this sort of thing - this all happens at the java
awt/swing/X layer.
> Regards
>
> ________________________________________________________________________
> In order to protect our email recipients, Betfair Group use SkyScan from
> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>
> ________________________________________________________________________
> --
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
>
More information about the 389-users
mailing list