Connection was already enabled but failed with error 651.

The IP address showing in the first screen is an APIPA address (169.154....) This kind of address appears only when DHCP is not available, and Windows then proceeds to provide itself an IP address automatically. In fact, APIPA stands for Automatic Private IP Addressing, and you can read more about it at Webopedia if you like. What's important here is that your ISP won't or can't tell you how to access its IP services, including DHCP. Weird! I'd be thinking about finding a new ISP, if I were you.
HTH,
--Ed--

Caledon Ken said:

Do you have your setup papers from when you got device. It will have info on it.

The device came only with a paper entitled 'Residential Broadband Service - Installation Acknowledgement Note', which included no instructions for settings.

Caledon Ken said:

Could you post link

https://www.google.com.hk/search?q=%...iw=918&bih=409

Thanks.

Could you please follow these instructions and report back. Hopefully this gets you rolling but I'm still unsure where IP address gets assigned. Hopefully I wioll learn something too.

http://www.tp-link.com.au/FAQ-921.html

Sure. No problem.

So you use Solution number 1. Did you get any messages as you went through process?

No messages had popped up.



The above screenshot was taken a minute ago. The Chinese text above 'Public network' means 'Unidentified network', but I can still access the Internet via Broadband Connection.

Public Network means you are outside a trusted LAN and your Firewalls are set to not allow sharing from other devices on Network. The other option is Private which means you trust the computers and devices within the LAN.

You might try a Network Reset. It is always possible that your Ethernet driver maybe incorrect. Do you have an older driver you could use?

Do you have an Image of your previous set up before your clean installed? I ask as you could get settings and driver version.

In your original screen shots there are no Gateways listed. To set these normally you go Static but I heard you, you never had to do this. Really you are more patient than I, I would be on phone to supplier requesting support and even escalating within organization.

I've asked the forum for some help. Maybe a fellow member has seen this before.

Hi.
I am not the best on this subject, but it sounds to me like the modem may be setup as a "bridge". I think in this case, the public broadband connection happens. To get DHCP/Firewall/NAT functions, you would need to add a router to the mix. The router then would connect to the modem using your username and password, and provide an internal IP address and firewall/NAT protection.

Also I noticed the Subnet Mask shows as 255.255.0.0 - that usually is 255.255.255.0. This could be a result of the APIPA Ed mentioned (I am not sure).

If you know what the modem's default gateway is, you could try these settings (this assumes the modem's gateway is 192.168.1.1):
IP Address: 192.168.1.2 (This is, in effect, setting a static IP behind the modem, and depends on your modem's gateway address.)
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.1 (if this is indeed your modem's gateway address, could be different.)
Preferred DNS server: 8.8.8.8
Alternate DNS server: 8.8.4.4
Shut down computer, power down modem, power up modem, turn on computer.

It's possible it could be something as simple as the ethernet cable going bad. Have you tried replacing the cable with a known-working one?

Also, can you connect another system to the modem without problems? If so, it could be your Network Interface Card in your system that is going bad.

If the cable is good, and another computer has the same problem, then it is your modem. Sometimes the ISP can send a reset signal, and sometimes it needs to be replaced.

That's about the best I can do without a user manual.