Vista and the mysterious unidentified network

We’ve been having problems with this since Vista came out, luckily it’s not a terribly frequent occurrence.  A new year has started and we’re seeing it again.  We currently have 2 students who cannot connect to our network, they keep getting the unidentified network with a 169.254 IP.  We have tried everything we can think of:

  1. release/renew just times out
  2. disable/re-enable the nic
  3. checked all the TCP/IP settings & checked the LAN settings
  4. typed netsh interface ipv6 show neighbors into the cmd prompt to see if anybody on campus was broadcasting as a gateway
  5. I’ve even gone into the registry to disable the broadcast flag.  NOTHING HAS WORKED.
  6. Setting the network type to private instead of public if it’s even set wrong.

I’ve spent hours and hours researching this online but so far have only come up with a couple more things to try.  One of which is doing a TCP/IP stack repair and the other just deals with disabling firewalls (windows and otherwise).  Has anybody actually found a solution that works?  This is driving me insane.

Edit #1: It appears that Norton and possibly McAfee cause some sort of problem.  I’m not exactly sure what yet.  We’ve tried disabling both programs, but that didn’t work.  A student uninstalled Norton and was able to get online.  I like those programs less and less the more I work with them.

Edit #2: We came across another one of these and they had some weird panda anti-virus software, uninstalling it got them online.  So if you come across this problem try uninstalling the anti-virus/firewall and see if that fixes it – just disabling them hasn’t worked.  I really wish I knew what specifically about those programs caused the problems.

, ,

  1. #1 by tlsharma on February 5, 2009 - 6:28 PM

    Try the following:
    Disconnect from all Networks if using wireless and unplug any cables if connected hardwired.

    Open the command prompt as administrator

    At the prompt type in “route delete″ > Hit Enter you will see”ok!”.

    Close the command prompt window

    Reconnect to the Network or plug in the cables and let the system acquire an ip address.

  2. #2 by Diego on October 17, 2008 - 5:59 PM

    I’m having the same issue, and I’ve tried a million things. This is ridiculous. Good luck on that

  3. #3 by productman on September 24, 2008 - 4:42 PM

    You try a different cable or port? Or statically assigning the IP to see if it’s communicating?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: