quote:Originally posted by TK: They say the NOC is near Atlanta.
speedtest.net says my ISP is Pan Am Sat, and thinks the NOC is in London, UK. /QB]
Maybe it is actually Atlantis - the lost city!
Emerged from inner peace long enough to test a bit. Found that my 3100 is still on my former IP address even though I was online when service seemed terminated Friday morning. I can telnet to it. However, it is flaky and keeps rebooting itself, so thinking some of the config files might have gotten corrupted. Sometimes the D3 can see it, sometimes not (probably during the reboots). I was able to locate 101W, but once it said the search was complete, no Rx lock.
Sounds like I am indeed in purgatory limbo. ooooohhhhhhmmmmmm.....
posted
Originally posted by Joe Keenan: So, I'm back up on 123W again
Good, that makes at least three of us!
Part of the problems I had last night was with trying to upload a sat table to the D3. Locked the D3 up a couple times. Not sure what the problem is. Do I need to stow the dish before doing that upload?
No.
As I understand it, you need to power cycle the D3 after loading the sat table.
I've heard that, but haven't found it to be true. For example, I was pointed at 101 when I learned I needed to be pointed to 123. I don't load an entire table - I make a custom one that only goes 15-or-so degrees each way from the target - so 123 wasn't in my D3. I loaded a new custom table that went across both 101 and 123, and hit search. It definitely used the new table, because it found 123 without problems which would have been impossible with the old table.
posted
TK, you are clearly going to need an options file e-mailed.
If you watch the telnet you will see the reboot is not a matter of being flaky - it will wait only so long after boot with no RX and then it says something like "Giving up, scheduling restart" and it reboots. I don't know if you need rmtstat set in order to see that message or not - I had it on.
John Watson was actually on 101 until late on Friday, but he never got a new options file pushed either, so his IP remains the same.
Also, be advised the Hub Network operators (making all of these changes) may have PUSHED you the new 123W options file (read: sent you the config file UDP over-the-air). I would say that if you LOST RX LOCK it is highly likely that you have the new config in the box and just need to repoint.
For those of you in INVESTIGATIVE mode, you can use iSite to extract your ACTIVE options file from the box and view it in NOTEPAD. There is a config block mid-way down (in the options file) for [MODEM INSTALLATION]. There should be a line in there with your spacecraft longitude (see below for what the line will look like).
If you do not see -123 in that block, then you are probably still on the 101 (-101 will be in that block instead of -123).
If you decide to check make sure you are looking at an options file that you retrieved from the box (after you lost Rx lock) because there is a good chance it was PUSHED to you.
[MODEM_INSTALLATION] spacecraft_long = -123.0000
You can also look your current config thru telnet by running an options show command.
posted
Yes, it displays the "giving up, scheduling O/S reboot" message in the normal telnet stream. Anxiously awaiting my turn in the queue, and I hope they find a bigger upstream pipe from what was reported earlier. 100-200 Kbps isn't going to cut it - I'd prefer something closer to 500 Kbps.
UPDATE - using iSite, I see I still have 101W in options file.
posted
Terri, Please give me or a Scott a calll today. We should be able to get you connected. We will start moving everyone now, please call my office line 801-478-8376 or 8355, Keep in my mind that this process will take us a few days, so if you don't get to me or Scott right away, please leave us your name and number so we call you back. We again recomend that you have Isite 7.1.1 on your system to facilitate this process. We have a couple other techs helping us with this process to try to reduce the amount of down time. Hey Don, thanks for thread, and thanks for the help the other day.
Franco.
Posts: 64 | From: Salt Lake City | Registered: Jun 2007
| IP: Logged |
posted
One more thing. Regarding the UPstream speeds. It should be resolved once we get everyone settled in and the remainng cards are moved from SES to Intelsat. Thanks guys for your patience on this matter.
Posts: 64 | From: Salt Lake City | Registered: Jun 2007
| IP: Logged |
posted
Interesting way out here on the Outer Banks of NC, when locked on 123W the reflector on the dish is almost vertical. Looks like 123W is about the longitude of San Francisco.
This means in the eastern US, trees, hills and such will be more of an issue compared to birds closer to mid-continent. Based on that, I hope they might move us mobile folks to G17 at 91W.
But for now, just glad to be locked on; will be happier when upstream speeds pick up as Franco suggested earlier.
posted
All is well here in Tyler Texas on 123. The Rx SNR is 15, very good. Tx power that I am sending is about -22. That's only about 5db higher than my max power (from the last 1db compression check), so it would appear that in this area the bird is a little deaf. That tracks with identical results that I was questioning with another system in Dallas on a different provider but still on 123.
Franco sent me a config file, I loaded it with iSite and pointed the D3 to 123, AND IT WORKED! Oh yeah... the config file has the new IP addresses and many remote systems with firewalls had to be reset... no sweat.
I am not wasting my time or your bandwidth with any tests, but the phone works and the VPN and SSL work so I am happy.
posted
Welcome to 123W. Were have you guys been all this time?
-------------------- F3/D3 3.9.4/iDirect3100/123W/40'EuroTrans 2003 Enterprise Server/10 Workstations/Blackberry 8830 Tethered to MBR1000 Where In The World Am I (click here) Posts: 272 | From: Boca Raton | Registered: Mar 2005
| IP: Logged |
posted
We're in Lebanon Mo today. Still in the high 60's for sq, & around 9 for snr. Am I lower than the other four on the 123W because of our .98 dish vs a 1.2 dish?