..yeah, all traffic seems OK, just for some reason Win 10 is keeping me from reaching inside LAN adressess... Lasts night I disable all firewalls, and rebooted, did not fix...
I also enabled "IP Routing" via the Registry, which was disabled from the Win 10 install, and rebooted, again no fix...
Exactly what do you mean by 'reach' and 'get to'? Do you mean that if you type its IP address in a browser you cannot get the router's web management page? Or do you by any chance have a shared drive on your router, say an external drive plugged into its usb port that you can't access in Windows 10 but could in Windows 7?
If it is a share you can't access, then you need to know that many routers that can share a drive in this way only support SMB1, and that SMB1 may be disable by default in Windows 10. If that is the case then you need to enable SMB 1.0/CIFS Client in 'Turn Windows features on or off'.
If you mean something else entirely, please explain what 'reach' and 'get to' actually mean, with error messages and/or screenshots if possible.
yeah, by "reaching" I meant typing the IP address in browser, and obtaining the router management page (actually the logging page, and upon logging in, the management page...).. no shared drives...
Here is error message from browser in Win 10
Hmmm… can't reach this page192.168.2.1 took too long to respond
Try:
Search the web for 192 168 2 1
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT
- - - Updated - - -
BTW -- I seem unable to post screen shots... when I take one, copy it to the clipboard, and then try to paste into reply message, it does not paste... however, I am able to highlight the text, copy it, and then paste... not sure what is going on there...
What happens if you "tracert" to an internal network address that you can't reach?
Checked your router security logs for clues on failure connections?
good ideas... below is output of tracert -- will need to reboot into Linux to check firewall logs on gateway ... will be a few minutes
C:\Users\njaim>tracert 192.168.2.1
Tracing route to pfsense.nja.localdomain [192.168.2.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms pfsense.nja.localdomain [192.168.2.1]
Trace complete.
@Bree -- ...funny you asked, I have Firefox installed as well, and same results.
@Steve --
...sorry for the delay
So had no log of blocks, and wrote firewall rule to track all allowed traffic from this machine. Looking a the new log, shows this machine allowed to access 192.168.2.1:80, so it seems the outgoing traffic from this machine reaching the gateway, but the return traffic from the gateway to this machine is not reaching my browser.. ?
...just tried this, and it is adding more to the puzzle...
While I can access the router/gateway via this machine, while in Linux with a fixed IP, I cannot access the gateway from my iPad either, going through a WAP, though the firewall logs in the gateway show all devices reaching it on port 80, but somehow the outbound traffic from the gateway back out is not reaching either Win 10, nor my iPad now... I am not a networking expert... but did not change anything except install Win 10 on new HDD...
- - - Updated - - -
...LOL... will you take 50 CAD ?
What is router model this is a common problem a lot of routers run JavaScript and it can be blocked as it can be seen as a threat
Quote
