 |
|
 |
|
|
|
|
|
|
|
|
|
Fred McKenzie
Guest
|
 Posted: Sun Aug 10, 2008 2:46 pm Post subject: Time Capsule Problem |
 |
|
I purchased the 1TB Time Capsule to replace an AirPort Extreme. Everything seemed to be working fine. It took a while until my hard drive was backed up using Time Machine. But then I tried to print to my AppleTalk printer connected to one of the Time Capsule's Ethernet LAN ports. It didn't work!
I tried adding a new printer, but it did not appear in the list under AppleTalk. The only way I could get it to work was to use the old AirPort as the Base Station, and configure the Time Capsule to extend an existing wireless network. In this configuration, the printer is connected to a LAN port on the AirPort Extreme.
The latest firmware was installed on the Time Capsule before the problem was observed.
Has anyone else had this problem? Did Apple outsource the Time Capsule to a company that doesn't know how to support AppleTalk?
I realize that AppleTalk is "frowned upon" by many IT people because its continual chatter uses network bandwidth. However, that bias stems from a time when networks were MUCH slower than they are today.
Fred |
|
| |
|
|
|
|
|
|
|
|
Gregory Weston
Guest
|
| Posted: Sun Aug 10, 2008 4:22 pm Post subject: Re: Time Capsule Problem |
|
|
In article <fmmck-C747C5.14463310082008@nntp.aioe.org>, Fred McKenzie <fmmck@aol.com> wrote:
| Quote: |
I purchased the 1TB Time Capsule to replace an AirPort Extreme. Everything seemed to be working fine. It took a while until my hard drive was backed up using Time Machine. But then I tried to print to my AppleTalk printer connected to one of the Time Capsule's Ethernet LAN ports. It didn't work!
...
Has anyone else had this problem? Did Apple outsource the Time Capsule to a company that doesn't know how to support AppleTalk? |
Does your ethernet printer have an address that's compatible with the TC's?
| Quote: |
I realize that AppleTalk is "frowned upon" by many
.... ignorant ...
IT people because its
.... alleged ...
continual chatter uses network bandwidth. However, that bias stems from a time when networks were MUCH slower than they are today. |
|
|
| |
|
|
|
|
|
|
|
|
Fred McKenzie
Guest
|
| Posted: Sun Aug 10, 2008 10:37 pm Post subject: Re: Time Capsule Problem |
|
|
In article <uce-729FDC.16225810082008@newsclstr03.news.prodigy.net>, Gregory Weston <uce@splook.com> wrote:
| Quote: |
| Does your ethernet printer have an address that's compatible with the TC's? |
Gregory-
Yes, if you mean an IP address. That is assigned via DHCP, the same as with the AirPort Extreme. However, I'm not sure an IP address is needed for AppleTalk to work.
If you mean an AppleTalk address, I don't know how that works. Why would it be different between the Time Capsule and the AirPort Extreme?
Fred |
|
| |
|
|
|
|
|
|
|
|
David Empson
Guest
|
| Posted: Mon Aug 11, 2008 4:14 am Post subject: Re: Time Capsule Problem |
|
|
Fred McKenzie <fmmck@aol.com> wrote:
| Quote: |
In article <uce-729FDC.16225810082008@newsclstr03.news.prodigy.net>, Gregory Weston <uce@splook.com> wrote:
> Does your ethernet printer have an address that's compatible with the > TC's?
Yes, if you mean an IP address. That is assigned via DHCP, the same as with the AirPort Extreme. However, I'm not sure an IP address is needed for AppleTalk to work.
If you mean an AppleTalk address, I don't know how that works. |
AppleTalk and IP are independent protocols with different addressing schemes. In network protocols terms, they use different Ethernet frame formats, so a router which looks specifically for IP (and related protocols) would ignore and discard AppleTalk packets. A simple "layer 2 bridge" should correctly forward AppleTalk along with IP.
AppleTalk generally uses self-assigned addresses, but you can manually configure them with some devices. On LocalTalk, only an 8-bit node address is used. On EtherTalk (or AppleTalk over Airport), a 16-bit network and 8-bit node are used, for an effective 24-bit address.
If you are familiar with the concept of 169.254 self-assigned addresses in TCP/IP (used in the absence of a DHCP server; sometimes called APIPA - Automatic Private IP Addressing), then AppleTalk operates on the same basic principle.
An AppleTalk station remembers its last used address and when it wakes up it does a broadcast to check if anyone is using that address. If someone else is using it, the station randomly generates a new address and tries that one instead. Rinse and repeat until a unique address is found.
| Quote: |
| Why would it be different between the Time Capsule and the AirPort Extreme? |
It shouldn't be any different. I've set up a couple of Time Capsules for other people but never tried to use AppleTalk with one so don't know if your problem is widespread or something specfic to how your Time Capsule is configured.
AppleTalk certainly works fine on my Airport Extremes and Airport Expresses (both G and N models of both).
On my Airport Extreme I have it going from either Ethernet LAN or wireless clients to the WAN port, which goes through to my main network switch. My AppleTalk printer is connected to that (HP LaserJet 6MP with JetDirect EX).
My Airport Extreme is configured to operate in bridge mode. This effectively puts the WAN port onto the same network as the LAN and wireless, and the Airport Extreme is operating as a layer 2 bridge.
If you had the Time Capsule configured to act as a DHCP server and/or use NAT, then its WAN port is a separate network, and it wouldn't surprise me if it won't forward AppleTalk packets between LAN (or wireless) and WAN, but this shouldn't affect its ability to forward AppleTalk between wireless and/or LAN ports (which is still just a layer 2 bridge). |
|
| |
|
|
|
|
|
|
|
|
Jolly Roger
Guest
|
| Posted: Mon Aug 11, 2008 11:54 am Post subject: Re: Time Capsule Problem |
|
|
In article <fmmck-C747C5.14463310082008@nntp.aioe.org>, Fred McKenzie <fmmck@aol.com> wrote:
| Quote: |
| I realize that AppleTalk is "frowned upon" by many IT people because its continual chatter uses network bandwidth. |
LOL! You're kidding me, right? Have you ever compared the chattiness of Windows file sharing services with AppleTalk? The amount of network bandwidth used byWindows file sharing services (which are *far* more prevalent on most IT-run networks) in every IT-run network I've ever used is simply enormous in comparison! |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
