The WGS 9650/350 Setting Up Addendum contains the following text:
"IMPORTANT Although you can simultaneously connect cables to the built-in AAUI and 10BaseT ports as well as the 10/100BaseT Ethernet port, you can use only one of these Ethernet connections at a time."
This is not entirely correct. A user can set up only one AppleTalk connection and only one TCP/IP connection. A user cannot set up AppleTalk or TCP/IP to use both the 10BaseT and the 100BaseT connections at the same time. However, TCP/IP can be enabled on one port while AppleTalk is enabled on the other.
Also, AppleShare IP 5.0 (included in some 9650/350 configurations) allows AppleTalk mutlihoming for the File Server (other components do not have multi-homing). AppleShare IP 5.0 does not do TCP/IP multihoming.
There is the potential for an administrator to configure AppleShare IP 5.0 and the 9650/350 in a way such that some clients experience a delay when logging in to the server.
If and only if:
- AppleShare IP is configured to provide AFP over TCP.
- AppleTalk multihoming is enabled.
- There is no TCP/IP route between the client, and the server's TCP/IP port.
In this situation, clients who have TCP/IP enabled, and are using AppleShare Workstation 3.7 to connect to the server's non-TCP/IP port, will attempt to ping the server prior to logging in. Because IP isn't routed between the client and server's TCP/IP port, the attempt will time out. The client software will then fall back to an AppleTalk connection. The user may notice a delay while waiting for the ping attempt to time out.