C
Colin Nash [MVP]
IP addresses in the 169.254.x.x range are automatically assigned by Windows
when it is unable to get an IP from a DHCP server. So your problem is
connectivity between those machines and the server. The workgroup is
irrelevant.
Check the network cables used by those two machines and make sure they are
being plugged into the proper ports on the hub. (i.e. make sure you aren't
using the uplink port with a standard patch cable, and if the uplink port is
being used by something else, the adjacent port may be disabled depending on
the design of that hub. There may even be a switch to toggle a port between
standard and uplink. Uplink is generally used to link two hubs together so
they act as one.) Windows 2000/XP will usually report when a network cable
is unplugged but don't rely on this because it can be fooled
when it is unable to get an IP from a DHCP server. So your problem is
connectivity between those machines and the server. The workgroup is
irrelevant.
Check the network cables used by those two machines and make sure they are
being plugged into the proper ports on the hub. (i.e. make sure you aren't
using the uplink port with a standard patch cable, and if the uplink port is
being used by something else, the adjacent port may be disabled depending on
the design of that hub. There may even be a switch to toggle a port between
standard and uplink. Uplink is generally used to link two hubs together so
they act as one.) Windows 2000/XP will usually report when a network cable
is unplugged but don't rely on this because it can be fooled