After finally being able to pick up a long enough ethernet cable, I figured I could just plug it in and go. Well, apparently not. I've already moved LAC to the top of the list in the network connections advanced settings and have tried disabling wifi entirely, power cycling, restarting, etc. No dice.
The cable works fine and it's picking up the modem according to the network connections page. The connections tab on my taskbar says I have internet access through wifi and wired, plus the network & sharing center says I'm connected to the internet with both as well. When I disable or unplug my wifi adapter, it stops saying I have internet access entirely.
No, I'm not paying for only wifi as my roommates have played on a wired connection for awhile. I'm not even sure if Comcast has a wifi only plan. Whatever.
I ran a windows network trouble shoot and it's telling me everything is properly configured, but the DNS server is not responding. ??? I've been trying to research this and haven't really found a solid way of fixing it. I remember using either OpenDNS or Google Public DNS and having it help (or work entirely, can't remember), but unless absolutely necessary, I don't really feel like relying on something else if I can just fix it to respond properly.
edit: Forgot to mention that while having LAC and wifi both enabled, my internet connection doesn't seem to act properly but fixes itself immediately after disabling LAC.
So there's my issue and a smaller issue that's more than likely the reason for my main issue. Please help me :(
After finally being able to pick up a long enough ethernet cable, I figured I could just plug it in and go. Well, apparently not. I've already moved LAC to the top of the list in the network connections advanced settings and have tried disabling wifi entirely, power cycling, restarting, etc. No dice.
The cable works fine and it's picking up the modem according to the network connections page. The connections tab on my taskbar says I have internet access through wifi and wired, plus the network & sharing center says I'm connected to the internet with both as well. When I disable or unplug my wifi adapter, it stops saying I have internet access entirely.
No, I'm not paying for only wifi as my roommates have played on a wired connection for awhile. I'm not even sure if Comcast has a wifi only plan. Whatever.
I ran a windows network trouble shoot and it's telling me everything is properly configured, but the DNS server is not responding. ??? I've been trying to research this and haven't really found a solid way of fixing it. I remember using either OpenDNS or Google Public DNS and having it help (or work entirely, can't remember), but unless absolutely necessary, I don't really feel like relying on something else if I can just fix it to respond properly.
edit: Forgot to mention that while having LAC and wifi both enabled, my internet connection doesn't seem to act properly but fixes itself immediately after disabling LAC.
So there's my issue and a smaller issue that's more than likely the reason for my main issue. Please help me :(
disable the wireless adapter and the ethernet adapter in the connections window thing
then re enable the ethernet adapter
and then do an ipconfig /reset /renew in cmd prompt.
disable the wireless adapter and the ethernet adapter in the connections window thing
then re enable the ethernet adapter
and then do an ipconfig /reset /renew in cmd prompt.
What's wrong with using Google's public DNS? I use it, even though the DNS automatically assigned to me beforehand worked just fine too.
flamedisable the wireless adapter and the ethernet adapter in the connections window thing
then re enable the ethernet adapter
and then do an ipconfig /reset /renew in cmd prompt.
also: ipconfig /flushdns
can't hurt, considering you're having DNS issues.
What's wrong with using Google's public DNS? I use it, even though the DNS automatically assigned to me beforehand worked just fine too.
[quote=flame]disable the wireless adapter and the ethernet adapter in the connections window thing
then re enable the ethernet adapter
and then do an ipconfig /reset /renew in cmd prompt.[/quote]
also: ipconfig /flushdns
can't hurt, considering you're having DNS issues.
Try the following things:
-Look for updated drivers for your motherboard's network adapter.
-Plug in to a different port on the router (preferably one of the ones a roommate uses).
-Use one of your roommate's cables on your computer, or if that won't stretch use your cable on a roommate's computer.
-Compare your IP settings on your computer to one of your roommate's (working) IP settings and make sure they match.
Try the following things:
-Look for updated drivers for your motherboard's network adapter.
-Plug in to a different port on the router (preferably one of the ones a roommate uses).
-Use one of your roommate's cables on your computer, or if that won't stretch use your cable on a roommate's computer.
-Compare your IP settings on your computer to one of your roommate's (working) IP settings and make sure they match.
#2 - I'll give that a shot.
#3 - Nothing wrong with GPDNS/ODNS, it's that I hate stuff not working properly. If push comes to shove, I'll ignore it and go back to using one of those two.
#4 - Does the port matter if the usb port lights up when it's plugged into that one? I would assume it's being picked up. My room is ~60ft away, which is why I needed to buy a cable. They don't have a computer. They had a PS3/4 but got rid of it not too long ago, so there's nothing in there to test it on.
#2 - I'll give that a shot.
#3 - Nothing wrong with GPDNS/ODNS, it's that I hate stuff not working properly. If push comes to shove, I'll ignore it and go back to using one of those two.
#4 - Does the port matter if the usb port lights up when it's plugged into that one? I would assume it's being picked up. My room is ~60ft away, which is why I needed to buy a cable. They don't have a computer. They had a PS3/4 but got rid of it not too long ago, so there's nothing in there to test it on.
First, make sure it isn't your cable.
Second, make sure you're getting your DHCP address assigned by the router. Look at your connection status, and click details. Your IP will probably be 192.168.something.something, or maybe 10.0.0.something. Make sure it isn't an "automatically assigned" address. (169.something I think)
Third, see if you can ping your router/modem. (Should be the IPv4 Default Gateway address under the details) Open command prompt (Windows + R, and enter 'cmd') and type 'ping 192.168.1.1', or whatever your default gateway is.
First, make sure it isn't your cable.
Second, make sure you're getting your DHCP address assigned by the router. Look at your connection status, and click details. Your IP will probably be 192.168.something.something, or maybe 10.0.0.something. Make sure it isn't an "automatically assigned" address. (169.something I think)
Third, see if you can ping your router/modem. (Should be the IPv4 Default Gateway address under the details) Open command prompt (Windows + R, and enter 'cmd') and type 'ping 192.168.1.1', or whatever your default gateway is.
mr64bitMake sure it isn't an "automatically assigned" address. (169.something I think)
Yeah, if it comes up as 169.254.x.x (link-local address), then you're not getting anything from the router's DHCP table.
[quote=mr64bit]Make sure it isn't an "automatically assigned" address. (169.something I think)
[/quote]
Yeah, if it comes up as 169.254.x.x (link-local address), then you're not getting anything from the router's DHCP table.
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hsd1.in.comcast.net.
IPv6 Address. . . . . . . . . . . : 2601:d:1e00:3ec:e029:b31d:77e3:6dde
Temporary IPv6 Address. . . . . . : 2601:d:1e00:3ec:c1ae:d4ad:bd8:c111
Link-local IPv6 Address . . . . . : fe80::e029:b31d:77e3:6dde%10
IPv4 Address. . . . . . . . . . . : 10.0.0.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::faed:a5ff:fe69:37e1%10
10.0.0.1
This is what comes up for it via cmd prompt. Not sure if that's the information you were referring to.
I went to ping my default gateway (10.0.0.1) and received this.
Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Ping statistics for 10.0.0.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
[quote]Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hsd1.in.comcast.net.
IPv6 Address. . . . . . . . . . . : 2601:d:1e00:3ec:e029:b31d:77e3:6dde
Temporary IPv6 Address. . . . . . : 2601:d:1e00:3ec:c1ae:d4ad:bd8:c111
Link-local IPv6 Address . . . . . : fe80::e029:b31d:77e3:6dde%10
IPv4 Address. . . . . . . . . . . : 10.0.0.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::faed:a5ff:fe69:37e1%10
10.0.0.1[/quote]
This is what comes up for it via cmd prompt. Not sure if that's the information you were referring to.
I went to ping my default gateway (10.0.0.1) and received this.
[quote]Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Ping statistics for 10.0.0.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms[/quote]
After talking with Fragile for a few about this, it doesn't seem to be a DNS issue since I'm still having it even after Google Public DNS got rid of the DNS error.
After talking with Fragile for a few about this, it doesn't seem to be a DNS issue since I'm still having it even after Google Public DNS got rid of the DNS error.
I managed to get it working somehow. Probably with some weird combination of things I've tried already. Thanks for the help, everyone!
I managed to get it working somehow. Probably with some weird combination of things I've tried already. Thanks for the help, everyone!