Search Again: Re: QuickDNS 3.0 From: Joseph D''Andrea Date: Tuesday, February 27, 2001 Time: 2:21:27 pm At 2:10 PM -0800 2/27/01, Men & Mice Support wrote: >Try quitting and relaunching Remote. (You can quit it with an >aptly-named item in the Utilities folder.) > >If that doesn't solve the problem, see if you can determine whether >Remote is listening, or if instead it's going deaf immediately after >launching. One way is to use a session watching program, such as >Interarchy or (I think) IPNetMonitor, to determine if there's an >open listener on TCP port 1337. I confirmed that qdns remote was running. I ran the port scanning tool from AGNetTools, and no port 1337. I quit remote with the quit applescript. Relaunced remote and bingo... connecting fine. Is this something that is expected or a feature. The reason I ask is this is a co-located box and we may not always have the ability to quit remote via TB2. Thanks, ___Joe___ _________________________________________________ Joseph D'Andrea JoeDan@West21.com WEST21.com Internet services for the 21st Century http://www.west21.com/ _________________________________________________

Messages In This Thread: Re: QuickDNS 3.0 by Men & Mice Support on Feb 27, 2001 at 2:10:51 pm Re: QuickDNS 3.0 by Joseph D''Andrea on Feb 27, 2001 at 2:21:27 pm Re: QuickDNS 3.0 by Men & Mice Support on Feb 27, 2001 at 2:39:31 pm Re: QuickDNS 3.0 by Suzanne Swift on Feb 27, 2001 at 2:43:26 pm Re: QuickDNS 3.0 by Joseph D''Andrea on Feb 27, 2001 at 2:49:46 pm Re: QuickDNS 3.0 by rob on Feb 27, 2001 at 3:14:41 pm Re: QuickDNS 3.0 by Men & Mice Support on Feb 27, 2001 at 5:27:04 pm