charrois Posted August 31, 2002 Report Share Posted August 31, 2002 Hi there. I have been using Retrospect 4.3 for quite some time on a MacOS 9.2 machine, backing up a combination of MacOS 9 and Windows machines, and things are working great. However, I'll soon be making the jump to OS X on the server, and so am considering to upgrade to Retrospect 5.0. However, I've read one thing that worries me considerably. Apparently, Retrospect 5.0 has dropped support for Appletalk, electing to only support TCP/IP. Is this true? The problem is that the machines in our little network here are operating under Appletalk, not under Appleshare IP. Though I'd love the much greater efficiency of using Appleshare IP, we do not have dedicated high speed Internet access here, and thus the computers all dial into the Internet when necessary by their own modem. As such, they are allocated an IP from our ISP when they're dialed in - a fixed IP isn't allocated to the computer for Appleshare IP to work within our local ethernet. I think that OS X allows us to have an IP allocated to the ethernet card, and another allocated by PPP when dialed in via modem, which would enable us to use AppleShare IP, but I'm not aware of any method to do this in OS 9. Does someone else have an idea? Basically, the problem is that I'm unaware of any method to run an Appleshare IP network over ethernet with OS 9 computers that individually need to dial into the Internet by modem and get an IP from our ISP from time to time (if someone knows of a way, please let me know!). And if I can't run Appleshare IP, I can't back up clients with Retrospect 5. And if I can't run Retrospect 5, I can't back up from my server which will soon be running OS X. Any help, solutions, or workarounds? There has to be a way of configuring things so that I can run an OS X server to network backup clients that need to be able to dial in to our ISP with their internal modems from time to time. When Retrospect supported Appletalk, I was able to work around the problem that way.. Thanks for your assistance! Dan Link to comment Share on other sites More sharing options...
ChrisYip Posted August 31, 2002 Report Share Posted August 31, 2002 Not sure if this is a viable solution but why not set up an internal LAN that takes care of your internet connectivity but sets up all your internal machines with private LAN IP numbers. That's what I did in my lab - I used Vicomsoft's Internet Gateway to set up one machine as a firewall and DHCP server. All my machines get DHCP licenses from it and all internet access is routed through it. I use Retrospect 5.0 on an OS X box and it can see all my Windows / OS X / Mac OS machines via TCP/IP. I'm even backing up two machines that are outside the firewall via their TCP/IP addresses (including someone's laptop) You could probably, depending in your situation, set this up with a hardware router (i.e. a cable / DSL modem router set up) rather than the software solution. HTH Chris Link to comment Share on other sites More sharing options...
charrois Posted September 4, 2002 Author Report Share Posted September 4, 2002 Hi there and thanks for the suggestion. I was hoping to be able to avoid dedicating a machine to Internet access for a couple of reasons - that computer would always have to be on all the time if any of the others in our little network wanted to connect to the Internet, and sharing a dialup connection between 3 or so people isn't the speediest thing in the world (right now, with each individual dialing up separately, at least they each get dedicated 56K connections - our ISP allows for multiple simultaneous connections). But it looks like either doing this, or upgrading all of the machines here to OS X might be the only solution I have. It's really too bad that Dantz dropped support for Appletalk in their latest software... I hate taking a step "backwards" performance-wise in our little network's Internet access to accomodate it, but I may not have the choice. Of course, this wouldn't be an issue at all if we had DSL or cable modem Internet access where I live.. Thanks for your reply! Dan Link to comment Share on other sites More sharing options...
jquiros Posted November 21, 2002 Report Share Posted November 21, 2002 keep it simple. you don't need a separate machine for yours to have ip addresses. you're overhyping "appleshare ip" too. like the previous poster said, just give each machine a private ip address, like 10.0.1.1, another with 10.0.1.2, another with 10.0.1.3, etc... and they'll see each other. when they dial up they'll use ppp. you're really making it much more complicated than it is. i hope this helps. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.