Getting Radmin working over local wireless
Getting Radmin working over local wireless
Author
Discussion

viper_larry

Original Poster:

4,377 posts

286 months

Sunday 10th September 2006
quotequote all
I have Radmin (Remote Administrator) server running on a test server in my home office which I connect to through my personal PC over the local LAN (Linksys WRT54G Router). All works fine.

However, the server is too noisy for the room, so I want to put it in the garage. Bought a USB wireless adaptor, installed and connects to my wireless network.

I can connect to the server with Radmin on both IP addresses when the LAN cable is plugged in, but when I take the LAN cable out, I cannot connect through the wireless IP. I have added IP forwarding to the router to the server, but no lukc getting a connection.

Is there something I am missing? It's very frustrating.

aldi

9,292 posts

267 months

Sunday 10th September 2006
quotequote all
Is there a setting within radmin to tell it which interface to bind to?

viper_larry

Original Poster:

4,377 posts

286 months

Sunday 10th September 2006
quotequote all
Not that I'm aware of, you simply use the IP address on the NIC you want to connect to. In this case, it's xxx.xxx.x.104 for the LAN and xxx.xxx.x.107 for the wireless. I've set up 2 different connections for the two IP's and can actually run both at once and see the same screen twice, until I pull the LAN plug that is!

GreenV8S

31,027 posts

314 months

Monday 11th September 2006
quotequote all
Strange. Can you ping it via the wireless IP after you disconnect the ethernet?

Edited by GreenV8S on Monday 11th September 00:03

viper_larry

Original Poster:

4,377 posts

286 months

Monday 11th September 2006
quotequote all
When the LAN cable is plugged in, I can ping both IP addresses. When the LAN is dosconnected, I cannot ping either!

There is no firewall running on the server.

GreenV8S

31,027 posts

314 months

Monday 11th September 2006
quotequote all
Is the wireless interface still up and running and bound to the same IP address? Also check the routes on the other client, it's possible that it's routing traffic for the wireless IP via the ethernet.