F5F Stay Refreshed Software Operating Systems IP configuration for Ethernet not set up properly

IP configuration for Ethernet not set up properly

IP configuration for Ethernet not set up properly

Pages (3): Previous 1 2 3 Next
T
Tijeyd
Member
Find
189
04-30-2016, 09:45 AM
#11
I've already tried that. I set it as the default gateway during my initial manual configuration to follow your instructions.
Reply
Reply
T
Tijeyd
04-30-2016, 09:45 AM #11

I've already tried that. I set it as the default gateway during my initial manual configuration to follow your instructions.

Reply
Reply
D
Dubzzy__
Junior Member
Find
2
05-01-2016, 11:48 AM
#12
Are you linking to a remote server or did you get configured on a managed network? The 169.254.xxx.xxx indicates your device was initialized using APIPA for a private IP address.
Reply
Reply
D
Dubzzy__
05-01-2016, 11:48 AM #12

Are you linking to a remote server or did you get configured on a managed network? The 169.254.xxx.xxx indicates your device was initialized using APIPA for a private IP address.

Reply
Reply
P
PahnterHD
Junior Member
Find
10
05-06-2016, 05:15 AM
#13
I'm not sure. The Ethernet cable is connected straight to the router. At first, I just installed the router, connected my devices, and everything functioned fine. I didn’t do any special setup or configuration—just plug and play, except for firmware updates on the router. I’m unfamiliar with APIPA and only have a basic understanding of IP addresses and subnetting.
Reply
Reply
P
PahnterHD
05-06-2016, 05:15 AM #13

I'm not sure. The Ethernet cable is connected straight to the router. At first, I just installed the router, connected my devices, and everything functioned fine. I didn’t do any special setup or configuration—just plug and play, except for firmware updates on the router. I’m unfamiliar with APIPA and only have a basic understanding of IP addresses and subnetting.

Reply
Reply
X
xWaffleGaming
Member
Find
69
05-06-2016, 06:08 AM
#14
Launch your command prompt via right-click and choose "Open as administrator." Enter these commands: netsh winsock reset catalog netsh int ipv4 reset reset.log. Restart the machine (select "Restart" in the start menu). Please inform me if this affected you.
Reply
Reply
X
xWaffleGaming
05-06-2016, 06:08 AM #14

Launch your command prompt via right-click and choose "Open as administrator." Enter these commands: netsh winsock reset catalog netsh int ipv4 reset reset.log. Restart the machine (select "Restart" in the start menu). Please inform me if this affected you.

Reply
Reply
G
Gagsu
Member
Find
195
05-06-2016, 03:56 PM
#15
Admin task completed. Proceeding with the request.
Reply
Reply
G
Gagsu
05-06-2016, 03:56 PM #15

Admin task completed. Proceeding with the request.

Reply
Reply
I
ItzOprayHD
Member
Find
173
05-14-2016, 04:44 PM
#16
That's a great point :-p I was just tweaking the post, thanks!
Reply
Reply
I
ItzOprayHD
05-14-2016, 04:44 PM #16

That's a great point :-p I was just tweaking the post, thanks!

Reply
Reply
T
tada_da
Member
Find
128
05-14-2016, 08:19 PM
#17
You're experiencing the same issue again, and it started after the update yesterday.
Reply
Reply
T
tada_da
05-14-2016, 08:19 PM #17

You're experiencing the same issue again, and it started after the update yesterday.

Reply
Reply
S
SoiKei
Member
Find
126
05-22-2016, 07:43 AM
#18
It functions properly now.
Reply
Reply
S
SoiKei
05-22-2016, 07:43 AM #18

It functions properly now.

Reply
Reply
M
McBroke
Member
Find
168
05-22-2016, 11:06 AM
#19
Great news! A bug in the Windows 10 update was fixed, resolving the strange problems. 😊
Reply
Reply
M
McBroke
05-22-2016, 11:06 AM #19

Great news! A bug in the Windows 10 update was fixed, resolving the strange problems. 😊

Reply
Reply
S
Stan_Labrie
Junior Member
Find
4
05-22-2016, 04:18 PM
#20
I'll watch for your reply and let me know it helped. After rebooting, make sure you select "Restart" clearly—Microsoft advises this. When you return to Windows, verify your IPv4 settings are correctly set to auto; if not, switch to auto and then disable/enable the NIC again.
Reply
Reply
S
Stan_Labrie
05-22-2016, 04:18 PM #20

I'll watch for your reply and let me know it helped. After rebooting, make sure you select "Restart" clearly—Microsoft advises this. When you return to Windows, verify your IPv4 settings are correctly set to auto; if not, switch to auto and then disable/enable the NIC again.

Reply
Reply
Pages (3): Previous 1 2 3 Next