Re: outbound traffic to unknown addresses using ports 134, 137, an

On Wed, 27 Jun 2007 08:48:03 -0700, Matt <Matt@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

It isn't always 169.254.x.x sometimes it changes to other addresses. But,
they are always unreachable and tend to be somewhere around the same numbers
(i.e. 168.254 or 167.254). What is the APIPA scheme? Also, we do not run
DHCP servers anymore. We cut those out of our network recently since even
the ones we were running were being setup to give IPs to certain specific
computers. The only DHCP that ever gets run is only turned on when we do
Jumpstart or Kickstart builds on Linux and Solaris.

Matt W.

See http://www.faqs.org/rfcs/rfc3330.html

You probably need to disable some interfaces on your client workstation.
Unused interfaces (like firewire) will assign themselves a network address
in the 168.254.x.x range if they can't find a DHCP server. If the
interface is set up with a service like NETBIOS over IP, then they will
attempt to send out traffic, which usually ends up going out the default
network interface.
.

Relevant Pages