Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dj0qn

Pages: 1 ... 143 144 [145] 146 147 ... 149
2161
I still think that my first theory was right....you did not change your RRC port from
port 80 to another port. You must do so, since otherwise trying to access your
network over DynDNS will try to open port 80 on your router.

To access, you must put the port number in your browser, e.g.
http://XXXXX.dyndns.org:YYYY, where YYYY is the port number.

Please reread my instructions from before, I already explained this.

73,
Mitch DJ0QN / K7DX

2162
Guy,

I meant the settings on the radio RRC and in the PC Client,
not the operating system. It would be good to compare.

Thanks & 73,
Mitch DJ0QN / K7DX

2163
Ok, thanks, Jan.

Also, hopefully the other guys will mention how they got it to work.

73,
Mitch DJ0QN / K7DX

2164
Hardware is version 5.
"Program Mode" is 5 - TS480.

2165
I didn't report a problem and try it out earlier, since the
forum reports were that it didn't work with the TS-480.

Then I read that the new version works, so I tried it out and can't
get it to work, so that's why I am asking for the settings from the
other guys.

The instructions are not all that clear to me, and my radio RRC-1258
COM2 setting doesn't allow it to be set in logical parallel with COM0, it
goes back to inactive. I understood that this setting is necessary
to allow HRD to access the TS-480 and the 2nd com port on the Micro
Client. I assume that I misunderstood something.

73,
Mitch DJ0QN / K7DX

2166
Guy,

I still can't get it to work after lowering the baud rate. I must be missing
some setting. It would be great if you and Thom were to provide a list of
correct settings.

Thanks & 73,
Mitch DJ0QN / K7DX

2167
It is not that easy to understand where your exact problem lies,
but I would venture to guess that you either didn't change the
port of your RRC-1258 server, or you are not trying to access the
port number with your browser.

A simplified procedure would be (radio side):

-  change IP address to fixed internal address that fits your subnet.
   Alternatively, set the MAC address in your router's DHCP server to
   always give the same IP address. This is needed for port forwarding
   or to place into DMZ later.

- Log onto the RRC-1258 and change the following:
1) Web server port to something not used
2) Maybe change SIP port, since 5060 is built into many routers
    and often has a conflict.
3) Enter your DynDNS account information
4) Suggest you change the web page user and password as well

- Then go into your router and forward the RRC-1258 ports (SIP,
   web server, etc.), or place into DMZ

- To access your RRC-1258's web page afterwards to configure
   RemoteRig, enter the following into your browser:
   http://XXXXX.dyndns.org:YYYY
   where XXXXX is your account/URL and YYYY is the port number
   Inside of your network, you enter http://192.168.XX.XX:YYYY
   where XX is your internal IP address, YYYY the port

If you still can't figure it out, I would be happy to give you a phone call
or Skype to go through this. I am 7 hours ahead of you.

73,
Mitch DJ0QN / K7DX

2168
Thom,

Could you please give the settings you used to make this work?
I installed the new beta and 2.27, but it still doesn't work.

Thanks & 73,
Mitch DJ0QN / K7DX

2169
I received the OK from HRO to post the following:

The RC-480KIT will become available in about two weeks at
the list price of $399.95.

The kit contains: The mount, mounting base, screw set,
cable and the control head.

Also, they will offer a limited special offer over Thanksgiving
weekend for a RemoteRig-set + TS480 radio + RC-480KIT.

73,
Mitch DJ0QN / K7DX






2170
General discussion forum / Re: Micro PC & DynDNS
« on: 2010-11-12, 13:20:59 »
Nicola,

If I understand you correctly, you have two RemoteRig servers,
but can only access one over the DynDNS address.

I would assume you know that you must assign two different SIP
ports, otherwise it won't work. In this case, you must forward
the second port in your router.

For example, the first box may be just iz7anl.dyndns.org, but
the second one would be iz7anl.dyndns.org:5601.

The micro client has the port number below the IP address,
so that is where the 5601 in this example would appear.

73,
Mitch DJ0QN / K7DX

2171
Hi Guy,

I also am now sure that the problem was caused by DynDNS being
down at the time of my update. The problem appears to be error
recovery in the box, since it didn't update again once DynDNS
started working again

I have several addresses with DynDNS and the service works
just fine. Seems that they had a hiccup.

73,
Mitch DJ0QN / K7DX

2172
I received a new shipment date from HRO: the first week
of December. I sure hope this doesn't slip again, since I would
like to bring my order back with me from my trip to the U.S.
over the holidays.

There is still no price as well.

73,
Mitch DJ0QN / K7DX

2173
The USB cable must be used to change the box to either a fixed internal
IP address for your subnet, or to DHCP to get an address from your
router automatically.

After you change it, you then must put the ethernet cable between
the box and your network and enter the internal IP address of the box.

If DHCP,  you may need to read this address in the DHCP table in
your router, unless you have few devices connected and can guess it
(e.g. 192.168.1.10, 192.168.1.11, etc.)

It will not work unless you change the IP address or to DHCP first, since
the default IP address will not work in your network (unless you have subnet
192.168.0.xx), nor will it work when you directly connect the box to your PC.

Note to Mike: there seem to be a lot of standard networking questions
that pop-up, it would make a lot of sense to add a network FAQ to the
manual. Your setup section does not appear to be enough.

73,
Mitch DJ0QN / K7DX


2174
I would check to see if it does indeed continue retrying, since that
is the only plausible explanation of why I had this problem, but no
one else did.

Yes, I was one of the guys that reported the web page accessibility
problem with 2.25 (and only with 2.25!). 2.26 has definitely
solved this, it hasn't died once since I installed 2.26.

73,
Mitch DJ0QN / K7DX

2175
Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?

If it gives-up, then this would mean the problem was coincidentally with
DynDNS at the time I installed 2.26 and simply changing the password, etc.
has no effect. You must disable/re-enable or recycle the power. This would
also explain why only I had that problem.

Since 2.26 solved the stability issue with the web page accessibility, I had
no reason to recycle the power since installing it.

73,
Mitch DJ0QN / K7DX

Pages: 1 ... 143 144 [145] 146 147 ... 149