>
Are you still receiving these errors? What is the full error message with
this code?
Thanks,
Mark
Usenetserver Support Team
On Mon, 21 Sep 2009 11:16:54 -0400, a�igMeanie <_@_._> wrote:
>On 21 Sep 2009 14:29:50 GMT, UNS Support <sup...@usenetserver.com>
>wrote:
>no code. it doesn't error out. but, it takes multiple tries to
>authenticate and then it shows connecting to 74.209.131.11 port 9090
>or the current ip for anywhere from 3 to 10 minutes before it
>actually connects.
>
>this happens each time the client tries to connect even if it's only
>been a couple minutes from the last connection.
> On 21 Sep 2009 14:29:50 GMT, UNS Support <sup...@usenetserver.com>
> wrote:
>
> no code. it doesn't error out. but, it takes multiple tries to
> authenticate and then it shows connecting to 74.209.131.11 port 9090
> or the current ip for anywhere from 3 to 10 minutes before it
> actually connects.
>
> this happens each time the client tries to connect even if it's only
> been a couple minutes from the last connection.
>
Things appear to have stabilized. Are you still having issues?
Thank you,
Mark
UNS Support Team
> On Mon, 21 Sep 2009 11:16:54 -0400, a�igMeanie <_@_._> in
> usenetserver.support with message-id
> <su5fb55gcu0p1g486...@4ax.com> wrote:
>
>>On 21 Sep 2009 14:29:50 GMT, UNS Support <sup...@usenetserver.com>
>>wrote:
>>
>>no code. it doesn't error out. but, it takes multiple tries to
>>authenticate and then it shows connecting to 74.209.131.11 port 9090
>>or the current ip for anywhere from 3 to 10 minutes before it
>>actually connects.
>>
>>this happens each time the client tries to connect even if it's only
>>been a couple minutes from the last connection.
>
> I have needed to change ports a lot lately. I did not have this
> problem in the past.
Things appear to have stabilized. Are you still having issues?