posted
Hello all, I've see a few of these posts, and tried what I've found, but I seem to be stuck at a slightly different step than most people.
Setting my IP to 192.168.0.4 I can access my D3 controller in "debug" mode only. If I browse to it I get an upload new firmware page. If I telnet in I can connect. I'm issued the nvclear command. It processes fine, says the at the ip address is now 192.168.1.250.
But that's all I can do. From what I've read, the next thing is to shut it down, restart it, change your computer's IP to 192.168.1.X and telnet in to the new address (192.168.1.250). I can't, it just times out. If I browse to that address, I get nothing. I tried browsing/telnetting to the old address, but again nothing.
The router lights and socket lights on the D3 are on indicating a connection, I've swapped cables, and power cycled about 100 times. Still nothing.
Oh, one more thing that I haven't seen mentioned, and that is that the LAN light on the front of the D3 is flashing. I can't find anything about that anywhere, anyone know what that means?
Thanks!!!
Posts: 7 | From: Colorado Springs, CO, USA | Registered: Jun 2010
| IP: Logged |
posted
Not sure if this will work on windows, but it works on a Mac.
Open a command (terminal) window, and try "ping 192.168.0.255" and "ping 192.168.1.255". You'll get some messages back about responses from various IP addresses. This is on a Mac, but it'll look something like:
$ ping 192.168.1.255 PING 192.168.1.255 (192.168.1.255): 56 data bytes 64 bytes from 192.168.1.109: icmp_seq=0 ttl=64 time=0.077 ms 64 bytes from 192.168.1.126: icmp_seq=0 ttl=64 time=0.305 ms (DUP!) 64 bytes from 192.168.1.117: icmp_seq=0 ttl=255 time=0.313 ms (DUP!) 64 bytes from 192.168.1.205: icmp_seq=0 ttl=64 time=2.058 ms (DUP!) 64 bytes from 192.168.1.250: icmp_seq=0 ttl=255 time=5.318 ms (DUP!) 64 bytes from 192.168.1.135: icmp_seq=0 ttl=64 time=89.369 ms (DUP!)
Now you know what IP addresses on each network on active. See if any of them are the D3 (telnet or browse).
joe
-------------------- Cradlepoint MBR95, Sierra USB-250U (Sprint WiMax) 2008 Newmar King Aire 4562, 2012 Jeep Liberty Limited Jet We're here! Posts: 731 | Registered: Nov 2007
| IP: Logged |
posted
ok, so my router congig is standard it's set to 192.168.1.1. DHCP: 192.168.1.2-50
I switched my computer to "auto", it got assigned 192.168.1.2
Still no luck browsing or telneting.
About the IP addresses, I'm looking into that, there is actually a way to do something like the macs can do.
Run this in the command prompt:
FOR /L %i IN (1,1,254) DO ping -n 1 192.168.1.%i >>c:\ipaddresses.txt
It'll take a while, but when it's done open c:\ipaddresses.txt and search for: 0%
That should get you the active IPs, or at least the ones that respond to ping.
For the IP address (192.168.1.%i) you can change it to 192.168.0.%i.
if you're looking for telnet servers you can use this:
FOR /L %i IN (1,1,254) DO telnet 192.168.1.%i
It will loop until it connects.
----------------
I haven't done an exhaustive search like that. I think that there is something wrong with the configuration somewhere and I'm just not getting though. I also checked in the router, and there's a diagnostic for seeing network activity and stripping out the IPs, my computer was the only active IP, the modem, which works and is connected, didn't even show up. I guess it just sits there unless you access it (or have it connected to the internet).
I also tried ping and traceroute from the router, no luck there either, it says there's nothing there.
So, I switched it back to debug mode. Still nothing on the routers activity monitor and can't ping or telnet from the router.
I switched the router to be in the 192.168.0.x block, which moves my computer aswell. But now with the router on that, I can't see the D3 even when it's in debug mode. This new finding makes me think that it may have something to do with the router.
But I moved the router to the 192.168.2.x block, and moved the computer to 192.168.1.5 and I still get nothing from 195.168.1.250.
So, I'm still stuck. Sorry for the long post, I'm far from an expert on this as I'm sure you can tell, I was really just messing with settings hoping that something would just happen to work.
Thanks!
[ July 14, 2010, 10:17 AM: Message edited by: Beachhouse ]
Posts: 7 | From: Colorado Springs, CO, USA | Registered: Jun 2010
| IP: Logged |
posted
Your modem should be attached to the WAN port of the router, so it will never show up on the LAN, active or not. Since it is 192.168.0.1 and is also a DHCP server you definitely do not want your router's LAN on the 192.168.0.x block!
I would do another nvclear, and then ignore the " From what I've read, the next thing is to shut it down, restart it" part of your first post. I'm not sure if any instructions say that, but the controller should take care of that on its own. Not sure if that is part of your problem.
Put the router on 192.168.1.x and let your computer get an automatic address then see if you can ping the controller.
I wanted to close this out, since I know how up setting it is not to know how things turned out.
I talked to Don at Oregon RV Satellite Service (http://www.oregonrv.net/)
He checked things out and said that my D3 controller was bad. So nothing I really could have done to make my system work the way it was. It was still covered under warranty, so he swapped it out with a D3 he had in his shop.
Works great now. I'm making this post off of my newly working dish!
Thanks too all the members and mods for posting here and helping me get my dish working!
Kanan
Posts: 7 | From: Colorado Springs, CO, USA | Registered: Jun 2010
| IP: Logged |
UBBFriend: Email this page to someone!
Printer-friendly view of this topic
