Wired connection, internet stuck at "Identifying", 169.XX IP problem

Thx - it was probably just me having a bad day with English.

So having it twice does not seem to be an issue.

There is usually a place with the router's interface that lets you assigned DNS IP addresses. Those DNS IP addresses should be automatically assigned to each computer that gets its IPs from the router via DHCP. You might try setting those fields to OpenDNS's or Google's DNS servers.

I don't recall and I don't have time right now to scan the thread again:
What happens if you set a static IP address on one of the computers that can get online?
That should let us know if the router just does not like computers with static IP addresses.

:::back later:::

n00boxular said:

......I'll try and ask some friend's to check their connections to make sure this same DNS server issue isn't just on my router or something.

Or take the laptop and a lan cable to another home as a test.

UsernameIssues said:

.............
I don't recall and I don't have time right now to scan the thread again:
What happens if you set a static IP address on one of the computers that can get online?
That should let us know if the router just does not like computers with static IP addresses.

:::back later:::

Never mind. I see where you already did something like that.
Can you please post a current screenshot of the screen shown in this post?

UsernameIssues said:

take the laptop and a lan cable to another home as a test.

Will do as soon as I have time, exams.

UsernameIssues said:

Never mind. I see where you already did something like that.
Can you please post a current screenshot of the screen shown in this post?

Please give the firewall used also as i requested.

Just to clarify on DNS it is always best to use your ISP's DNS servers in your router or free DNS servers in your country locale if ISP dns servers are unknown or know n to have issues.

Your gateway IP address as the DNS server cannot resolve hostnames and tries and connects to a DNS server in the hope of a response.

Windows firewall is being used.
Also, if you read the whole thread putting ANY DNS IP doesn't work. My isp isnt providing any DNS server to me either.

Also, could you clarify the last sentence?

Let me try and explain Your gateway IP address as the DNS server cannot resolve hostnames and tries and connects to a DNS server in the hope of a response since I was going to need to mention how this part should work:

There are computers that keep lists of IP addresses. We call these computers DNS servers. When one of the computers on your network asks for sevenforums.com, the DNS server returns with 184.172.52.100 and your computer connects to 184.172.52.100.

Your router does not keep this rather massive table of IP addresses. When one of your computers requests sevenforums.com, that computer sends a DNS query to your router. Your router then sends that request to whatever DNS server your ISP told it to use. That DNS server tells the router that sevenforums.com = 184.172.52.100. The router tells your computer that sevenforums.com = 184.172.52.100, The router is nothing more than a relay.

When your computer asks for an automatic configuration from your router, the computer is assigned an IP address and DNS servers. In this case, your router is assigning 192.168.1.1 two times as the DNS servers to use.

For the sake of simplicity, we will say that your router connects to your ISP. The router asks for an automatic configuration from the ISP. The router is assigned an IP address and DNS servers. Somewhere in the router's interface you might find a status page that tells you what IP address and what DNS servers the router was assigned.

So, having bored you with all of that, here are some things to try:
In the screenshot, there is an empty field named Primary DNS server address. Put 8.8.8.8 in that field and 8.8.4.4 in the secondary field. Doing this may cause your router to restart (it does on my router). Then restart a computer that can get online. Let that computer gets its IP address and DNS info via DHCP. The router should now assign 8.8.8.8 and 8.8.4.4 as the DNS servers that each computer on your network should use. Check to see if those DNS IP addresses now appear in the ipconfig info for the computer that you just restarted. Also check to see if that computer can surf the net.

If it does have 8.8.8.8 and 8.8.4.4 as its DNS servers AND if it can surf the net, then it seems like it is the router that is preventing traffic from DNS servers that it did not assign to computers on your network.

If it does have 8.8.8.8 and 8.8.4.4 as its DNS servers BUT it cannot surf the net, then it seems like it is your ISP that is restricting which DNS servers may be used*.

All of the above does very little to help us to know why a wired network adapter fails to get an IP via DHCP and yet a wireless network adapter on the same computer works via DHCP. The hope is that if the router is doling out 8.8.8.8 and 8.8.4.4 as DNS servers via DHCP, then maybe the router will not reject 8.8.8.8 and 8.8.4.4** if they are manually assigned to the failing wired network adapter. Confused yet



*Now, if the ISP seems to be blocking certain DNS servers, then look around in the router's interface for the DNS server addresses that the ISP assigned to the router... or contact your ISP and ask for the DNS server addresses. Put those addresses into the field named Primary DNS server address and Secondary DNS server address. Then restart a computer and see if you can surf.

**Those DNS servers are really slow for me. I use OpenDNS for my DNS servers. If you get bored some day, you can read this: How do I test DNS lookup latency with ns_bench? SBC DSL FAQ | DSLReports.com, ISP Information

Well, at long last I was finally able to fix this problem. Turns out my router had some weird ass configuration and was assigning my port to a internet service I hadn't subscribed to. So my laptop was requesting service, but since I hadn't subscribed to it, I was getting nothing. Whats even more weird is that it was only happening to my laptop even tho several other PCs were connected using that port. Soft and hard resets were useless for some reason.

I contacted my ISP and explained the problem to them and they removed the service from my router. Everything is working fine now, no need for static IP addresses. Static IP addresses wouldn't have worked anyways because Saudi Arabia blocks a lot of websites and the ISP didn't want to give me their DNS servers or allow me to change which DNS I could use. This was their reasoning for not giving me the DNS servers. Thank you all VERY much for the detailed and quick responses.

TL;DR for those who want a quick solution: Too bad, read the whole thread, you might actually learn something.

Glad you got it working and thanks for posting back with the resolution.