Quote
Quote from: nvjar on Today at 02:09:25 AM
I have tried to trouble shoot for days but I can't seem to get to my cubes settings page.
<snip>
I'm pretty sure I'm just missing something small but I'm pretty new to this so if you know what I did wrong and can explain like I'm 5 it would be appreciated.
I don't see anything wrong with your settings on your router, but please note that I haven't dug around in a non-Apple router in years. Speaking of which, I wonder if you should have static DNS servers set? As noted above, Google's DNS server at 8.8.8.8 is highly regarded.
Have you tried pinging your Cube? This would tell you for sure whether or not your PC is seeing your Cube. You can ping from the Windows Run app. I found a tutorial with screenshots for Windows 7 in case you are unfamiliar with this: http://www.wikihow.com/Ping-in-Windows-XP
The short version is you would type ping 192.168.1.254 in the Run app, and it will then spit some stuff back at you. If your PC can find your Cube, it will spit back something like:
Code:
64 bytes from 192.168.1.200: icmp_seq=0 ttl=100 time=7.777 ms
You can read more about pinging at that link, on wikipedia, etc.
If it doesn't see your Cube, it will timeout, or maybe give you some hits with really high times (in thousands of ms) interspersed with timeouts. That would mean you have some issues on your network, like an IP conflict.
I have tried to trouble shoot for days but I can't seem to get to my cubes settings page.
<snip>
I'm pretty sure I'm just missing something small but I'm pretty new to this so if you know what I did wrong and can explain like I'm 5 it would be appreciated.
I don't see anything wrong with your settings on your router, but please note that I haven't dug around in a non-Apple router in years. Speaking of which, I wonder if you should have static DNS servers set? As noted above, Google's DNS server at 8.8.8.8 is highly regarded.
Have you tried pinging your Cube? This would tell you for sure whether or not your PC is seeing your Cube. You can ping from the Windows Run app. I found a tutorial with screenshots for Windows 7 in case you are unfamiliar with this: http://www.wikihow.com/Ping-in-Windows-XP
The short version is you would type ping 192.168.1.254 in the Run app, and it will then spit some stuff back at you. If your PC can find your Cube, it will spit back something like:
Code:
64 bytes from 192.168.1.200: icmp_seq=0 ttl=100 time=7.777 ms
You can read more about pinging at that link, on wikipedia, etc.
If it doesn't see your Cube, it will timeout, or maybe give you some hits with really high times (in thousands of ms) interspersed with timeouts. That would mean you have some issues on your network, like an IP conflict.
Here are the results when I ping the cube and from an IP scan.
This doesn't seem to even read the cube as being functional. If there weren't lights flickering I would have thought it was DOA.