|
|
|
People often mistake me for an adult because of my age.
Keep calm, and carry on posting.
Referral Links: Sharesies -
Are you happy with what you get from Geekzone? If so, please consider supporting us by subscribing.
No matter where you go, there you are.
trig42:
Just to get it straight.
Have you tried another Ethernet device (ie., NOT your PC) on that cable? Does it get a valid IP address (not 169.254.x.x)
Have you tried another Modem?
Have you tried a different cable direct to the Modem?
Have you tried a factory reset on the Modem?
I have tried another PC via LAN to this modem with same cable, it works. Have also sent data over GbE lan to a laptop via this PC so no, lan is fine.
I don't have another modem, yes have tried reset.
Mobo is Asus Z97-A with on-board Intel Ethernet Connection I218-V, which I just tried removing from device manager, uninstalling driver and installing the latest from the Intel website. same thing.
My guess is when I installed another network device (i.e. the wireless adapter), win7 did some retarded stuff which caused this problem, & even if the new device is uninstalled the new protocols causing the problem will be left behind.
OK.
How did you send data over GbE LAN to a laptop from the PC? Did you put manual IP addresses into each?
Have you tried putting manual IP/Gateway/Subnet and DNS in to see if that works?
If you do not want to believe that your PC LAN port is dead, have you tried downloading a Linux LiveCD OS or WinPE disc and booting to that? Or reinstalling Windows?
As I said previously, I have seen the exact symptoms you are seeing quite a lot. In nearly every case, it is a faulty NIC, which means motherboard replacement (or getting a PCI/PCIex LAN card).
trig42:
OK.
How did you send data over GbE LAN to a laptop from the PC? Did you put manual IP addresses into each?
Have you tried putting manual IP/Gateway/Subnet and DNS in to see if that works?
If you do not want to believe that your PC LAN port is dead, have you tried downloading a Linux LiveCD OS or WinPE disc and booting to that? Or reinstalling Windows?
As I said previously, I have seen the exact symptoms you are seeing quite a lot. In nearly every case, it is a faulty NIC, which means motherboard replacement (or getting a PCI/PCIex LAN card).
autoconf ip would be fine for Win7+ transfers.
as above screenshots, autoconf in usage so makes sense too...
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
trig42:
OK.
How did you send data over GbE LAN to a laptop from the PC? Did you put manual IP addresses into each?
Have you tried putting manual IP/Gateway/Subnet and DNS in to see if that works?
If you do not want to believe that your PC LAN port is dead, have you tried downloading a Linux LiveCD OS or WinPE disc and booting to that? Or reinstalling Windows?
As I said previously, I have seen the exact symptoms you are seeing quite a lot. In nearly every case, it is a faulty NIC, which means motherboard replacement (or getting a PCI/PCIex LAN card).
I sent data from PC to laptop with auto everything, no manual IP - it just worked as they were on the same Workgroup. Is it possible for a NIC to be able to send data but have this sort of error (i.e. be partially stuffed)?
I have not tried putting manual IP entries into LAN IP... probably worth a try. I know the values and range for IP/gateway, but then I have to enter values for DNS servers, what should they be?
I have not tried re-installing windows and would rather shoot myself :D Buying a PCIe NIC is a definite option & will do that tomorrow if all else fails.
can you log into your router via the wifi adapter, and post a screenshot of the dhcp part, as i'm fairly sure that's where the problem is
miztic:
can you log into your router via the wifi adapter, and post a screenshot of the dhcp part, as i'm fairly sure that's where the problem is
done but there's not much info there - remember these settings work with lan on another PC

I'd try LAN interface settings, IP address: 192.168.1.1
Can you give us a screenshot of the page where you saw "I can also see the PC listed as a connected ethernet device in the modem gui."
Just to confirm, does the PC still show zero packets received on its wired LAN?
OK... TYPING THIS FROM LAN! It be fixed lol. Here's what I did:
1. Powered down & pulled the wireless. 2. after no change, setup manual IP including Spark's DNS servers. After some reading have also set a manual metric on the Gateway to 1, not sure if that's necessary though... 3. Reset the modem again. All good :)
Ran speed test, 1ms ping & 460Mbps upload, nice... The first download attempt was only 130 for some reason? Second test 915 where it should be. Just in time for Friday beers lol.
arcon: After some reading have also set a manual metric on the Gateway to 1, not sure if that's necessary though...
It has been. ![]()
The DNS addresses don't care - they have only different response times. (most are Google and they are fast - for the price they know you are looking for in the internet).
|
|
|