In response to Andrew Rodger�s long epistle of problems with his printers, Macs and an ADSL connection, this is a problem which it is realistically very difficult to advise on via a mailing list like this � it�s too complicated and there are two many further questions that need to be asked (like how does the Satellite Proxy server work, and what does your comment about the G4 being given a �full hosting ID� actually mean!) , the answers to which would determine any suggestions. You may need to get a consultant in to look at the setup on your site, assess the problem and possibly do a bit of trial and error/diagnostic work to resolve it all. It�s always possible, of course, that someone else has encountered exactly these problems and setup before and knows exactly what�s wrong, but I certainly can�t fully answer your questions based on what I know so far.
However, one thing which I would suggest trying is to statically assign IP settings to all the systems (including the printers) to make sure that they are all in the same subnet and have the same settings for subnet mask etc. Before you can do this you will need to know what local IP address the router is set to. This can be determined in a number of ways � the simplest way is to look in the Network pane of System Preferences (for MacOS X), or the TCP/IP Control Panel (for MacOS 8 or 9). I am sure from your comments that you know enough that I don�t need to explain this any further! You can then statically assign all the systems to be in the same subnet (ie with the first three groups of numbers in the IP address the same, only the last one being different for each system), with a subnet mask of 255.255.255.0, and the Gateway address set to the local address of the Router. You will also need to find out an address for your ISP�s DNS if you want internet connectivity to work properly (get this from their website while you know that you still have a working configuration on one of the systems), although this will not matter for resolving your immediate problems within the local subnet. This will ensure that all IP-based communications are set up correctly. You may think that this would not have any effect on �AppleTalk� based connections, but in fact certain connections that use AppleTalk to set up the connection (in the discovery part of the connection establishment), actually use TCP/IP to communicate once the connection is established. This is most commonly the case for file-transferring connections. For this type of connection you sometimes get a phase of the establishment of the connection where you get a dialogue saying �Trying to connect� or suchlike which eventually times out. This would occur where TCP/IP settings are not correct for the two systems to talk to each other, even though they can see each other using AppleTalk. Normally the connection will fall back to AppleTalk after a timeout period, but this doesn�t always happen correctly. I totally can�t guarantee that this will resolve the problems you are experiencing, because I don�t think there is enough information in your description of the symptoms to fully know what the problem is. However it�s one step along the way and it may resolve some, at least, of the problems. I have glossed over one or two subtleties in the above to ensure that the posting isn't too vast - it could be twice as long if I explained everything fully! Nick -- Nick Collingridge - Zapp Computer Consultancy -- Mac UK is sponsored by <http://lowendmac.com/> and... 123Inkjets.com <http://lowendmac.com/ad/123inkjets.html> Support Low End Mac <http://lowendmac.com/lists/support.html> Mac UK list info: <http://lowendmac.com/lists/mac-uk.shtml> --> AOL users, remove "mailto:"; Send list messages to: <mailto:[EMAIL PROTECTED]> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive: <http://www.mail-archive.com/mac-uk%40mail.maclaunch.com/> Using a Mac? Free email & more at Applelinks! http://www.applelinks.com
