View Single Post
  #4  
Old 30-07-2011, 11:41 PM
mithrandir's Avatar
mithrandir (Andrew)
Registered User

mithrandir is offline
 
Join Date: Jan 2009
Location: Glenhaven
Posts: 4,161
Quote:
Originally Posted by OICURMT View Post
This leads me to believe that one of your computers is expecting a DHCP server to assign it an addy... you should make sure that both computers have static IP addresses in the same class range (Class B in your example). You will also need to check your firewall setting between the computers (turn it off temporarily to make sure it is not interfering).
169.254.51.212 is strictly speaking not a class B address, even with the class B netmask. 169.245.1.0-169.254.254.255 is the IPv4 Link Local address block as defined in RFC 5735 and RFC 3927. See Wikipedia if you don't want to read the RFCs. Link local autoconf is the fallback for when DHCP fails.

Not getting a suitable address is the symptom. The solution depends on how the network hangs together. A firewall should not be stopping DHCP or autoconf. A diagram would help.

Andrew
Reply With Quote