Hi,
Have an old proprietary unix based IBM workstation (Scitex Brisque 4.1 RIP for those familiar with it). It runs an Appletalk unix application (don't know if that is the correct term) allowing Macs to connect to it and mount volumes residing on it. Files can then be copied to it from the Mac.
Everything was running great until we upgraded two of our Macs to OS 10.5 (one an Intel and one PowerPC, both at 10.5.8). Now when we try to connect to the workstation using "Connect to Server" we get a "Connection failed There was an error connecting to the server....".
We do get the "Enter your username and password...." dialog box and enter the same user name and PW as usual, but then get the "Connection failed" message. It must do some communication with the workstation because it uses its name in the "Enter your username and password...." dialog box.
The "Make AppleTalk Active box is checked with Configure: Automatically" in Network Preferences on both 10.5 Macs (as well as other 10.4 Mac).
Does anyone know of something that might have changed in AppleTalk in 10.5 causing this problem?
Have an old proprietary unix based IBM workstation (Scitex Brisque 4.1 RIP for those familiar with it). It runs an Appletalk unix application (don't know if that is the correct term) allowing Macs to connect to it and mount volumes residing on it. Files can then be copied to it from the Mac.
Everything was running great until we upgraded two of our Macs to OS 10.5 (one an Intel and one PowerPC, both at 10.5.8). Now when we try to connect to the workstation using "Connect to Server" we get a "Connection failed There was an error connecting to the server....".
We do get the "Enter your username and password...." dialog box and enter the same user name and PW as usual, but then get the "Connection failed" message. It must do some communication with the workstation because it uses its name in the "Enter your username and password...." dialog box.
The "Make AppleTalk Active box is checked with Configure: Automatically" in Network Preferences on both 10.5 Macs (as well as other 10.4 Mac).
Does anyone know of something that might have changed in AppleTalk in 10.5 causing this problem?