Satellite LE sudden network problem

[Dan Pinder]

Everything's been just dandy for the past month in the following configuration, until yesterday and I cannot get the two to talk:

Mac Pro (intel) running PT|HD 8.0.3cs1 on Mac 10.5.8
internet connection to Ethernet port 2 (IP today is 192.168.1.100, subnet mask 255.255.255.0)
Cat 5 cable connected from Ethernet Port 1 on Mac Pro to Intel MacBook Pro
Both MacPro and MacBook Pro set to DHCP.
Satellite port 28282 on both machines.
MacPro Ethernet port 1 is self-assigned IP: 169.254.227.152, Subnet 255.255.0.0
MacBook Pro has self-assigned IP 169.254.194.147, subnet 255.255.0.0

Teleport works, as does File Sharing. I have tried many times, in vain, to create manual IPs for Satellite.

Can some force for good write me out a definitive, quick start network setup using this hardware configuration? I came in this Monday and all of a sudden—nothing. I feel like I should be able to set manual IPs on this "private" network I've created, but that has never worked.

[Nathan W.]

Make sure your TCP/UDP Port numbers are the same on your HD system and Satellite. Happened to me once, accidently had two different numbers.

[Dan Pinder]

Originally Posted by Dan Pinder

Satellite port 28282 on both machines.

[Nathan W.]

Might require a HUB to work. I use a HUB Gigabit connection...

[Nathan W.]

There's a page with the Satellite option UPDATE for the satellite too...kinda hard to find not sure where it is. Look on the forums for the link. might want to run that just in case. I'd also delete all your preferences and databases see if that works.

[Postman]

I'm curious how it ever worked reliably.

Mac Pro port 2 looks right for a typical LAN. It is one of up to 252 computers on a local network. You've got email!

MacPro port 1, with a separate cable to your MacBook, is another story. Where did those numbers come from? When DHCP is enabled as it is on both of your computers, some device somewhere on the network that both of machines are connected to must be assigned as a DHCP server, otherwise trouble.

Bob Brown will have to chime in here, I think there is a limitation as to how wide the subnet can be. 255.255.255.0 is safe within the same local network, but 255.255.0.0 with those "self assigned" IPs may be beyond what they've allowed for.

[Dan Pinder]

Originally Posted by Nathan W.

Might require a HUB to work. I use a HUB Gigabit connection...

Ordered one from Engineering—should be here tomorrow sometime.

[Dan Pinder]

Originally Posted by Postman

I'm curious how it ever worked reliably.

Mac Pro port 2 looks right for a typical LAN. It is one of up to 252 computers on a local network. You've got email!

MacPro port 1, with a separate cable to your MacBook, is another story. Where did those numbers come from? When DHCP is enabled as it is on both of your computers, some device somewhere on the network that both of machines are connected to must be assigned as a DHCP server, otherwise trouble.

Bob Brown will have to chime in here, I think there is a limitation as to how wide the subnet can be. 255.255.255.0 is safe within the same local network, but 255.255.0.0 with those "self assigned" IPs may be beyond what they've allowed for.

A little more documentation wouldn't go amiss for this product. It's like, either make it fully discoverable or "plug & play" or document it further and give specifics!

[Postman]

Hopefully Bob will jump in with actual knowledge, since I could be completely off base again.