[WIP] setting up fileservices, VNC, and possibly game servers

[A_flyboy]

This started originally as an "I'm stuck" thread, but is now more shifting towards "current project".

Currently working on SSH tunneling to connect fileservices because apparently, FTP is "special" and needs to be babied to bounce off my business website. VNC on the other hand worked almost instantly, and still works, and generally is cool and doesn't care.

As a fringe benefit, I have a second machine that is just sitting around doing nothing, will soon be converted over to a full time dedi serv host.
Currently waiting for SSH installation by Godaddy. Then I will attempt SSH tunneling; shall we start a pool on experiment success vs. cascade failure and aliens?:zoid:

=== original OP problem==

ok... to start, some definitions to explain this:

site: www.abc.com
host: godaddy
home IP: x.x.x.x

I'm trying to use a subdomain on my site, say home.abc.com, to redirect to my home server at x.x.x.x. For the moment, I'm trying to run both tightVNC, and filezilla fileserver on the server, and connect to both.

I first tried .htaccess 301 redirects, but after hours of not getting anywhere, tried a DNS A record instead.
On my website hosting account, I configured a [I]DNS A record:
[/I][TABLE="class: grid, width: 500"]
[TR]
[TD]host[/TD]
[TD]Points to[/TD]
[/TR]
[TR]
[TD]home[/TD]
[TD]x.x.x.x[/TD]
[/TR]
[/TABLE]

When I connect with VNC: woohoo it works!

When I connect with 4 different FTP clients, it decides to redirect to home.abc.com/x.x.x.x :suicide:

My end goal is to be able to connect to my FTP/VNC without having to babysit it and fix the ip every time I unplug the router, but to start, I'd love to know why FTP is mangling all my redirect attempts. Shouldn't it generally not care as long as it gets an IP?

Thoughts, suggestions, did I miss some obvious better way to do all of this?

[Killervalon]

If you go to filezilla.. use the quick connect address field and write home.yourdomain.tld (tld is something like .com .me .dk .de all that shit)
NO SLASHES NO ANYTHING EXTRA
make sure the port is 22 or else you'll have to change that in the field & write your login.. Then quick connect

Also why the fuck is this in Web Development & not technical support?

[A_flyboy]

I downloaded a couple FTP clients (one on Windows, 4 on Android) to rule out a simple program quirk. I [I]am[/I] using the proper address. home.dom.tld, the redirect should point at x.x.x.x.
It works fine on VNC, but for whatever reason, it redirects ftp traffic to [URL]ftp://home.dom.tld/x.x.x.x[/URL] instead of just [URL]ftp://x.x.x.x[/URL]

Per your suggestion, I'll go try to punch it in again, just to double check.

Given it involves networks, websites, servers, and file transfer; instead of the typical "what hardware failed on my gaming pc", I wasn't sure which it more fell under. Don't get all upset over it, help, move the thread, or ignore it if it so irks you.

Edit: update, it appears to be throwing an error 312: unsafe port. Looking into it now. -unrelated, due to HTTP

Edit: working on SSH as a solution.