Search Again: Re: can''t connect to server - followup From: Men & Mice Support Date: Wednesday, February 20, 2002 Time: 11:47:28 am 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: can''t connect to server - followup by Peter Duchateau on Feb 20, 2002 at 7:07:14 am Re: can''t connect to server - followup by Men & Mice Support on Feb 20, 2002 at 11:47:28 am Re: can''t connect to server - followup by Peter Duchateau on Feb 20, 2002 at 11:33:46 pm