I am trying to connect to a Mac OS X server running Timbuktu
Pro from a Windows NT 4 box running Timbukto Pro 2000.

The client is saying "Could not connect to the remote computer. Either
the remote computer is not running Timbuktu Pro or the address is not
valid."

However, if I try telnetting to the server's port 407 from the client
box, I CAN make a connection.

I have two questions: 

1. How can I get Timbuktu to work? Why isn't it working, even though I
AM able to reach port 407?

2. Are there any other cross-platform remote-desktop alternatives
besides VNC/TightVNC? Those have shown themselves to be too sluggish
to be useful; I'm hoping for something closer to the speed provided by
non-cross-platform services like Windows' and Apple's "Remote
Desktop", which don't just send raw bitmaps across the wire, but
instead send more abstract updates like "move this window here".

---

Request for Question Clarification by wengland-ga on 13 Jun 2002 14:43 PDT

Which version of Timbukto Pro are you running on the Mac OS X server? 
I presume it is 6.0 or greater.  You aren't running a 5.x version
under OS 9 Emulation, are you? 

---

Request for Question Clarification by wengland-ga on 13 Jun 2002 14:46 PDT

Also, have you upgraded to the latest version of Timbuktu Pro? 
Netopia claims the 6.0 version has some 'issues' with OS X and you
should upgrade to 6.0.1 

---

Request for Question Clarification by notyou-ga on 13 Jun 2002 14:46 PDT

I assume you've read the FAQs for Timbuktu Pro? 
 
<a href="http://www.netopia.com/en-us/support/faqs/software/osxfaq.html">http://www.netopia.com/en-us/support/faqs/software/osxfaq.html</a> 
 
Specifically, there's a note in there about toggling TCP/IP Incoming
Access off and on:
 
&gt; After running the Applescript to change the contact port that
Timbuktu Pro
&gt; uses, your OS X requires that you toggle TCP/IP Incoming Access off
and on
&gt; (Setup:Preferences:Incoming Access). After you re-enable TCP/IP
incoming
&gt; access, Timbuktu Pro will now reflect the new port 
 
Have you tried running it on other ports? 

---

Clarification of Question by placain-ga on 13 Jun 2002 15:33 PDT

On the Mac side, version 6.0.1. On the PC side, it's Pro 2000 build
805 RC 115.
 
I did turn on TCP access (if I hadn't, port 407 would be refusing
connections!)
 
I have tried running it on other ports (I tried 8000, which is
normally my webserver -- I shut down the webserver and ran Timbuktu on
that port, using Applescript to change the port). Same results -- it
runs, the port is open and can be telnetted to, but the client says it
can't connect. 

---

Clarification of Question by placain-ga on 13 Jun 2002 21:28 PDT

Nope... the Mac is a G4 iMac, the PC only has one nic. 

You haven't got anything out of the ordinary on either of these
machines such as multiple nic's by any chance have you?

Not a real answer, but as to the connectivity issue, I'd say you will
have the most luck contacting Netopia.

For remote application display, XFree86 (X Windows) running on the Mac
will be able to be displayed on the Windows box if you have an X
Server such as Hummigbirds HCL Exceed running on the Windows box. 
I've used this a great deal to manage Unix machines from a Windows
box.

However, I do not think it will remotely display the native OS X
applications, only X-Windows based apps.  If all you need is terminal
display, that'll work well.

I use Timbuktu Pro (latest Mac and PC versions) all the time between
OS X 10.1.5, OS X Server 10.1.5, NT 4 SP6a, Windows 2000 Server and
Pro, and XP.  I've seen this error when the Timbuktu service crashes
on NT, and stopping/restarting the service from the console will reset
things appropriately. (Of course, usually this happens in a lights-out
data
center, and the onsite tech droid will only know how to powercycle the
box...) I also stronglt recommend you to upgrade the Windows client to
the latest Pro 2000 build. I haven't checked in a few months, but
Netopis was up to build 877 and there were some significant
improvements. Good luck.