Jump to content

Recommended Posts

Posted

Hi,

Someone has brought me there laptop today from home saying it won't connect to the internet.

When I've had a look no matter if i use the network cable or wireless it always gets a 169 address. I know the school network is running fine. IP Address is set to auto.

Its vista.

Any ideas ?

Thanks

Posted
Hi,

Someone has brought me there laptop today from home saying it won't connect to the internet.

When I've had a look no matter if i use the network cable or wireless it always gets a 169 address. I know the school network is running fine. IP Address is set to auto.

Its vista.

Any ideas ?

Thanks

 

A 169.254.*.* address is called an APIPA address and is created by the machine when it cannot find a DHCP server.

 

Take a look here for a little more info: APIPA - APIPA in Computer Networking

 

Seems to me a problem with the connection somehow. I'd also make sure it's free of virus's and other crapware that might be causing the machine difficulties in networking.

Posted
Also, just a thought, but can you assign the machine in question a static address within your range and see if it can communicate with other network devices then?
Posted

Thanks.

No, i've set it with a static IP Address and its still the same. Aparently its the same at his house. The lights on the network card are 1 solid orange and 1 flashing yellow

Posted
Apartfrom obvious things like firewall settings and anti-virus - have you tried uninstalling the nic, updating the drivers etc, that often clears glitches. There again I might be way off the mark.
Posted

As its happening with Nic and Wifi I'd of thought its something to with firewall... Norton not hiding on there anywhere?

 

Try resetting the winsock etc?

netsh winsock reset catalog (reset winsock entries)

netsh int ip reset reset.log hit (reset TCP/IP stack)

 

Is Vodafone Mobile connect software installed on the laptop, I've had this interfear with DCHP allocation before now

Posted

All the above is good stuff, another thing to check is that the DHCP client service hasn't been disabled.

 

EDIT: I missed the bit about working with a static, sounds like a bad card or a driver problem.

 

Sling in a Linux Live disk and see if the networking works.

Posted

Im with pooley on this, it doesnt seem to be a problem with the hardware because its affecting both cards.

 

EDIT: As K.C.Leblanc says, try a live disc.

Posted

Tried resetting winsock etc

Try resetting the winsock etc?

netsh winsock reset catalog (reset winsock entries)

netsh int ip reset reset.log hit (reset TCP/IP stack)

 

Still the same.

 

Just downloading a live cd now to try

Posted

Hi

 

We have this a lot and it is generally down to a hardware lockout on the router (especially when it gets hot). Power down the router(s) for a few seconds and try again!

 

These can be very odd as anyone connected when the system "locks out" can reconnect fine just anyone that wasnt connected still cannot connect!

 

The other thing to check is on the DHCP server to make sure you have enough free addresses for the amount of systems on the network!

Posted
Have you checked the adapters properties to see if DHCP is enabled? Also, have you checked that TCP/IP filtering is disabled (or at least configured correctly)?
Posted
Thanks.

No, i've set it with a static IP Address and its still the same

 

This is the bit I don't get, if you have set a static IP how can it still be showing a 169. address?? Or are you saying that it has no connectivity?

 

Remember that the static IP needs subnet mask, gateway and DNS addresses to make it work.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...