djoye
2[H]4U
- Joined
- Aug 31, 2004
- Messages
- 3,115
This is on Windows 7 64bit and this issue seemed to start this past week.
For the longest time I had a static IP set on my Windows machine along with the subnet mask and gateway; I had the DNS configured to 192.168.1.1, the router. This worked fine for the longest time and then this past week I began noticing that web pages were loading slowly and sometimes incompletely. I had the same results in multiple browsers but when I'd boot to Linux I had no issues.
I tried to think of what was different between my Linux and Windows configurations; in Linux I didn't have the static IP configured so I went back to DHCP in Windows and my problem was solved. I then decided to try to dig further so instead of using the router IP for the DNS I entered my ISP's info in there (which the router has and I assume is referenced when Windows looks to 192.168.1.1 for DNS info). After entering the actual DNS servers in there it continued functioning properly.
The only changes made to the OS were MS patches and more specifically it could have happened after the Remote Desktop exploit was patched; I'm wondering if those could have contributed to the issue.
For the longest time I had a static IP set on my Windows machine along with the subnet mask and gateway; I had the DNS configured to 192.168.1.1, the router. This worked fine for the longest time and then this past week I began noticing that web pages were loading slowly and sometimes incompletely. I had the same results in multiple browsers but when I'd boot to Linux I had no issues.
I tried to think of what was different between my Linux and Windows configurations; in Linux I didn't have the static IP configured so I went back to DHCP in Windows and my problem was solved. I then decided to try to dig further so instead of using the router IP for the DNS I entered my ISP's info in there (which the router has and I assume is referenced when Windows looks to 192.168.1.1 for DNS info). After entering the actual DNS servers in there it continued functioning properly.
The only changes made to the OS were MS patches and more specifically it could have happened after the Remote Desktop exploit was patched; I'm wondering if those could have contributed to the issue.