Support
Authorization

Newsletter

  Settings

Few suggestions / bug report...

 

Search  Rules 
Close
Login::
Password::
Forgot your password?
Register
Login
 
Pages: 1
Few suggestions / bug report...
 
Hello,

I've been testing version 3 BETA for few days and here are some bugs I found and some suggestions. I'll be updating them ;) :

- It seems that the Scan for Active Servers option is not reporting servers if they are not listening on the default port 4899.

- As a File Transfert option it would be great to be able to save both Local and Remote path so we won't have to browse all again (as it's available on any FTP client)


Bye
 
Quote
It seems that the Scan for Active Servers option is not reporting servers if they are not listening on the default port 4899.
What port number did you set up? Is this port open in your firewall?

Quote

As a File Transfert option it would be great to be able to save both Local and Remote path so we won't have to browse all again (as it's available on any FTP client)
We've included this suggestion into our Wishes list.
Most of Radmin features are implemented according to our users' wishes. Probably it will be developed in further releases.


Best regards,
Roman Makarov.

Famatech
Technical Support.
 
Quote
David Chevalier wrote:
- It seems that the Scan for Active Servers option is not reporting servers if they are not listening on the default port 4899.
It will scan for servers on nonstand ports on hosts for which you have a connection in your phonebook set to connect on that port.

For example if \\warthog is running rserver3 on port 4898 AND you have a connection to warthog on 4898 defined in your phonebook, it will indicate the presence of the server with a checkmark through warthog's icon.

It may be that predefined connections aren't necessary to find servers running on the default port, but it makes sense that it can't check every possible port, so it apparently checks the port set up in your pre-defined connections and possibly others running on 4899 on the LAN, assuming it has some idea of what the LAN is.

I haven't tried this because I'd have to change several of my servers to listen on the default port, which is not my preferred configuration.
Jim
 
Quote
it apparently checks the port set up in your pre-defined connections and possibly others running on 4899 on the LAN
You're right.


Best regards,
Roman Makarov.

Famatech
Technical Support.
 
I desactivated any firewall.

Check the Pictures:

Radmin 2.2 (port 4899) / Radmin 3.0 (port 4900)
[URL=http://imageshack.us][/URL]

Radmin 2.2 (port 4900) / Radmin 3.0 (port 4899)
[URL=http://imageshack.us][/URL]

It's not able to see the listening port 4900. It will see the port 4899 either if it's hosted by Radmin 2.2 or 3.0.

Weird, isn't it ? :|
 
Quote
Roman Makarov wrote:
It's not able to see the listening port 4900. It will see the port 4899 either if it's hosted by Radmin 2.2 or 3.0.

Weird, isn't it ?
I've never tried defining two entries with the same IP. I wonder if it's finding the first one for a given IP. you could try reversing the order in which they appear in the phone book. Sort by port #. If that doesn't bring localhost 2 to the top, swap the connection names.

If it finds the one on 4900 but not the one on 4899, my theory is correct: It stops checking a given host (no matter how many entries there are) if it finds a server. This is not the behavior I would expect, but then I don't think it's common to have 2 entries for the same host. Also, I don't run 2.2 anymore. But it is installed so I may fire it up and try some experiments.

I can tell you it finds non-standard ports on hosts running rserver3 becuase I use 'em and it finds 'em.
Jim
 
I have notice this issue. I have 2.2 srv listening on one port and 3.0 srv listening on another. I create a pinhole in my DSL Router to the same address10.X.X.X and included both the 2.2 port and the 3.0 port in that pinhole but I can could not connect to either. I added a secondary IP address to the Nic then created a pinhole to the secondary nic using the 3.0 port and it worked. So 2.2 connects to primary IP using pinhole for 2.2s port and 3.0 connects to the secondary address using a pinhole with 3.0s port. This sounds similar to your issue when scanning for ports. I think it finds the first active port and stops looking.
Stacey Cline
 
Quote
Stacey Cline wrote:
This sounds similar to your issue when scanning for ports. I think it finds the first active port and stops looking.

I ran 2.2 3.0 together for a day or two, then turned off 2.2, since as far as I was concerned 3.0 was solid.

Do many people run both?

Jim
 
I run both on my machines and 2.2 runs on a different port from 3.0
Everything works as designed. Have no problems.
-Radek
Pages: 1
Users browsing this topic (1 guests)

Radmin 3.5

Windows 10 Compatible

DOWNLOAD

Free for 30 days

BUY NOW

Only $49 per lifetime license
for  50 PCs - $29.8 per remote PC
for 100 PCs - $24.9 per remote PC
for 150 PCs - $23.3 per remote PC
from 200 PCs - $22 per remote PC
Follow us on Twitter
Famatech Corporation Copyright © 1999-2015 Famatech. All rights reserved.