People can't connect on my IP
 

Hi,

I recently setup an linux computer using the following tutorial: http://secure-ubuntu-server.blogspot...watha-web.html
(I skipped step 6 because I didn't use an virtual host)

everything is working great on my local host. but other people can't connect to the external IP (got Ip from Ipchicken.com)

I forwarded my ports on my router (20,21,80,443,50000-50100), and added the computer to the DMZ list (just for testing if that would made any difference, but it didn't.)
but this link keep saying they're closed (http://www.yougetsignal.com/tools/open-ports/)

tested with 2 routers having same problem for both, different setup of linux though.
now using D-link DIR-300

For next testing I did:
didn't have any results on external connect, but when I close them I can't connect to the server with SSH,nor can I see the site.
so the iptables does affect the server

any suggestions, what could be the problem and how to fix it?

grt kiwi

Okay, so, how about dyndns instead? I suspect you're running some sort of Internet server here. Cool! The IP address is tricky as it renews/changes all the time. However, dyndns allows you to stay accessible even using an dynamic IP address. Check out their services!

Good luck

Thor

Check with your provider if they block ports.
Often they block ports for servers on dynamic ip's.

Kind regards

Yep they block the following ports:

0 -> 1023, 1080, 12345, 12346, 31337 -> 31339, 31784, 27374, 1243, 31785 -> 31792, 4444, 1847, 1900, 3127

How can I make that when you connect to the IP and get the mainpage?
Gonna look for myself now to, but if you know the answer feel free to reply

EDIT: They can already can connect to IP:2000 (I've set the port for hiawatha to 2000)
so now I need to make that they auto connect to that port when they connect to it

If ports 80 or 8080 are not blocked, all you need to do is set up a page called "index.htm" or something like that (see the settings in the server) and your visitors will see that page first...
But, 1 to 1023 seems to be blocked, so there's no option here. So, I assume dyndns to be an option. Set up a domain, delegate that to your IP : port and (possibly) presto! Look into the wizard they have...

he said "Yep they block the following ports: 0 -> 1023, ..." so its likely 80 is not getting through.

for OP, what "router" are you talking about? and what do you mean by "forwarded ports"? you also say "auto connect" for clients, the only way they will "auto connect" is if, as example, they save a url shortcut with fqdn[:]port in it.

Yep, did extract that out of the reply :D

@ OP - by the way, you may want to check with your provider's fine print. There is a healthy reason for these ports to be blocked: so you should not run a server...

I know that it's for security reasons but I mailed them asking if they would open it, probably not gonna work, but it's definitely worth the shot ;P
And for an dynds, I don't want to spend any money on this one, it's just for fun. or perhaps i saw the site wrong and it's an free service.

@Linux Kidd, as I said in first post it's an D-link DIR-300, and by forwarding I mean, I got to the page port forwarding, and add the ports, is there any other way then?

They will allow it if you take a fxed IP.

Kind regards

Seconding that, repo. However, a fixed IP address (with ALL the extra's that come with it) comes with a bill. Be warmed.

Depends on the ISP. TimeWarner in Texas only charges $5/mo for a static IP with their basic consumer internet package.
Comcast, on the other hand, won't give you a static IP unless you upgrade to their business class account, which is double the price...

if its a real business server then buy an IP. if its occassional access for friends and what-not then just use dyn-dns with a odd port like 2022 or 8080, whatever gets through the ISP, etc.