[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cobalt-users] Re[2] Qube2 responding too slow

I have played around with these settings, but currently they are:

Qube configured as a local DNS.
The Qube is not using itslef as primary DNS.
The PCs are using the Qube as their primary DNS.
Could this be the reason why it is responding so slow, even when I try just to check my local mail or accessing the Qube trough telnet? 

Thanks in advance.



Date: Sun, 22 Oct 2000 11:56:33 +1100
Subject: Re: [cobalt-users] Qube2 responding too slow
From: Malcolm McLeary <mmcleary@xxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Reply-To: cobalt-users@xxxxxxxxxxxxxxx

Hi Luis,

on 22/10/00 11:15 AM, Luis E. Norambuena at norambna-cb@xxxxxxxxxxxxxxxxx
wrote:

> Any hints about it?

Is you Qube configured as a local DNS?

Is your Qube using itself as its Primary DNS?

What are your PCs using as their DNS?

Cheers,  Malcolm

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

                       Information Alchemy Pty Ltd
                             ACN 089 239 305
                           Canberra, Australia

Malcolm McLeary                                Mobile:     0412 636 086
Managing Director                              Email:  mmcleary@xxxxxxx

     This message was sent using Outlook Express 5.0 for Macintosh.


--__--__--

Date: Sat, 21 Oct 2000 21:15:46 -0300
To: cobalt-users@xxxxxxxxxxxxxxx
From: "Luis E. Norambuena" <norambna-cb@xxxxxxxxxxxxxxxxx>
Subject: [cobalt-users] Qube2 responding too slow
Reply-To: cobalt-users@xxxxxxxxxxxxxxx

I had some problems with the setup of my Qube2.

  1.- Inbound and Outbound mails processing frequencies

Our Qube2 is acting as an internet gateway using a modem. So we want to
send internet email and retrieve new internet messages perhaps once every
hour. We have configured the e-mail server parameters to send and retrieve
messages once every hour. This works fine for us, because we don't want our
modem to dial the ISP very often. (this is outbound mail for me)

Now, we have 20 users in our Qube. Each of them has an email account, and
very often one 'Qube User' sends an email to another 'Qube User' (inbound
mail). In this scenario, we don't need the Qube to dial our ISP, because
the mail doesn't need to go to the internet, it will just remain inside the
Qube. But the user wants to get this kind of messages immediately and not
wait 1 hour before the Qube processes all messages.

So is there a way to tell the Qube to process all inbound mail immediately,
but send and retrieve 'internet mail' (outbound mail) for example only once
in an hour?

  2.- Qube is not responding fast many times.

It is absolutely clear that we need to wait for the Qube to connect to
internet via modem (in our scheme) if we want to reach an internet
resource. That is not a problem, the thing is that many times, when a user
just wants to check his mail from the Qube's Email Server, the Qube takes
very very long to answer this request. So long, that sometimes the User's
email client times out.

This does not happen all the time, but it happens. The network is running
fine, and when something like this happens, I ping the Qube from the very
same machine that is not getting the mail and the ping works fine. I don't
know if this has something to do with this or not, but when this problem
arises, I see the Qube trying to dial our ISP and it answers the users
request only after connecting to the ISP.

I had similar problems even trying to telnet the Qube. I get most of the
time an immediate response, but sometimes it takes very very long for the
Qube to answer.

This is of course our biggest problem. Any hints about it?


Thanks in advance.
--__--__--