 |  |
I just reinstalled from scratch and all is fine now.
Re: can''t connect to server - followup
From: Peter Duchateau
Date: Wednesday, February 20, 2002
Time: 11:33:46 pm
But it seems to that QDNS or QDNS Manager has a problem with AppleScript and
a larger(?) number of zones.
When I use the "add slave server" script it timed out at 225 zones, there
are 262 on our primary server. The first time I ran it, it just hosed my
setup. The second time I could just rerun the script.
When I use the "Zone Report" script it causes the server to hang.
But as I said, all is fine now.
Thanks for your support, Men & Mice and the list.
on 20-02-2002 20:47, Men & Mice Support at cbuxton@menandmice.com wrote:
> Best guess: Something got hosed. Restore from backup, then quit and
> relaunch QuickDNS Remote. If you don't have a backup, reinstall from
> scratch and try again - since this is a slave server, it should be
> easy to recreate the slave zone entries using the AppleScript.
>
> If you continue to have problems with this, please contact
> <mailto:support@menandmice.com>.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> support@menandmice.com Making DNS Easy
>
> At 4:06 PM +0100 2/20/02, Peter Duchateau wrote:
>> I found this in the list archives:
>>
>>> It sounds like Remote isn't launching properly. If the problem were
>>> the password, the error message would say so.
>>> Scan the machine in question for open ports; is port 1337/TCP
>>> listening? If not, then Remote is nonfunctional. (You can scan for
>>> open ports using Mac OS X's Network Utility.)
>>
>> So I made sure Remote was running on the server and did a port scan:
>>
>> Open Port: 53 domain
>> Open Port: 80 http, www-http, www
>> Open Port: 427 svrloc
>> Open Port: 497 dantz
>> Open Port: 548 afpovertcp
>> Open Port: 3272
>>
>> => no port 1337
>
Messages In This Thread:
Return to Digital Point Solutions' Home Page