|
|
 |  |
Re: Slow Server repliesFrom: Men & Mice Support Date: Wednesday, July 21, 2004
Time: 7:53:07 pmAt 11:50 AM +1000 7/22/04, Nicholas Orr wrote:
>When you try to connect it looks as if it's going to time out, and
>so you click cancel, and the admin app closes and quits completely.
What happens if you don't hit cancel?
>If this means it's Remote, then is it as simple as doing a
>reinstall? It's been restarted recently and that didn't affect it.
It's probably much simpler. Since you're able to connect from inside
your private LAN, QuickDNS Remote is working normally. So the problem
is most likely the IP address that QuickDNS Central has stored for
QuickDNS Remote - if you used the internal address when adding the
name server(s), QuickDNS Manager won't be able to connect to QuickDNS
Remote from outside your LAN.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
>On 22/07/2004, at 11:42 AM, Men & Mice Support wrote:
>
>>Probably not. When you added your name server(s), did you use
>>internal or public IP addresses?
>>
>>To approach the problem from a different angle, when you fail to
>>connect, after you dismiss the dialog, do you get the Connect to
>>Server dialog box again? If you do, then you're failing to connect
>>to QuickDNS Central. However, if you don't, then you're connecting
>>to QuickDNS Central successfully, but failing to connect to
>>QuickDNS Remote.
>>____________________________________________________________________
>>Chris Buxton Men & Mice
>>Customer Support Specialist Making DNS Easy
>>
>>At 7:06 AM +1000 7/22/04, Nicholas Orr wrote:
>>>I'm a little bothered by this, and I've noticed that it's slow on
>>>regular occasions, but I've never been able to figure out why.
>>>
>>>In an unrelated but just as confusing issue, I can connect with
>>>admin from inside the network, but not outside it, even though all
>>>of the correct ports are being forwarded. Could this be related?
>>>
>>>Nick
>>>
>>>On 22/07/2004, at 4:33 AM, Men & Mice Support wrote:
>>>
>>>>However, the first several attempts at using nslookup resulted in
>>>>a "no such server" error message. So ti took quite a while for my
>>>>local name server (running on my PowerBook, as it happens) to
>>>>look up the address of your server in the first place. At this
>>>>point, I can't tell why this happened.
|

Return to Digital Point Solutions' Home Page |