Launching a Socket Server

[gumOnShoe]

So, I've been testing locally for a while, but I'm to the point that I want to take my Java Socket Server and actually put it up on my domain.

I'm wondering if anyone has any experience. I picked a random port and it seems that the port probably isn't open? The socket binds to the port fine, but I can't connect from another location.

All I know is that its a virtual linux box, whatever DreamHost uses by default.

Thanks for the suggestions.

[TropicalPenquin]

Do dreams your host allow connections on ports that are not http/mail/ftp etc.

I can imagine most hosts will block all connections on ports that don't provide one of these functions for security reasons.

[gumOnShoe]

At 1/2/11 07:26 AM, TropicalPenquin wrote: Do dreams your host allow connections on ports that are not http/mail/ftp etc.

I can imagine most hosts will block all connections on ports that don't provide one of these functions for security reasons.

Supposedly. After talking to support it should be possible, but they wouldn't help me actually do it. I can find examples of people asking how to do it and doing it a few years ago, but nothing recent. So I'm wondering if it is security they've added since.

Anyway, I just found a hidden switch in their gui panel that allowed me to finally give myself root access. So I should be able to use one of the many commands I was unable to use before.

Suggestions on which ones I should try first would be great. I think I have to open the port myself, and it should be allowed. I'm taking a long flight today, so I'll read what's posted either tonight or tomorrow night depending on available time.

[gumOnShoe]

At 1/2/11 07:26 AM, TropicalPenquin wrote: Do dreams your host allow connections on ports that are not http/mail/ftp etc.

I can imagine most hosts will block all connections on ports that don't provide one of these functions for security reasons.

How do I check this?

I tried setting up a proxy server and I can get the server to fail (register a connection, but process it incorrectly) if I directly load the webpage tied to the server, but I can't telnet from my home pc.

[Jon-86]

At 1/9/11 11:16 AM, gumOnShoe wrote:

At 1/2/11 07:26 AM, TropicalPenquin wrote: Do dreams your host allow connections on ports that are not http/mail/ftp etc.

I can imagine most hosts will block all connections on ports that don't provide one of these functions for security reasons.

How do I check this?

Write a simple port scanner. Get it to incrementally connect to each port then log what happens. If its blocked the connection is typically refused but if their is some kind of service you will get a deamon message or some kind of welcom message telling you what service is running or at the very least an SYN ACK

[gumOnShoe]

At 1/9/11 03:05 PM, Jon-86 wrote:

At 1/9/11 11:16 AM, gumOnShoe wrote:

At 1/2/11 07:26 AM, TropicalPenquin wrote: Do dreams your host allow connections on ports that are not http/mail/ftp etc.

I can imagine most hosts will block all connections on ports that don't provide one of these functions for security reasons.

How do I check this?

Write a simple port scanner. Get it to incrementally connect to each port then log what happens. If its blocked the connection is typically refused but if their is some kind of service you will get a deamon message or some kind of welcom message telling you what service is running or at the very least an SYN ACK

Well, I finally did something reasonable. My server is a homebrew, which means there's probably something wrong with it. I went and downloaded Java's example knock knock client & server. I put one up on my webpage and kept the client on my pc. I can telnet to the knockKnockServer. I can hit it with the knockKnockClient. So it is now down to something with the way I wrote my server.

I'll have to find out what they did with one that I did not do with the other.