Connecting to my static IP

[tom1681]

I have a static IP with my ADSL ISP (Force 9 in the UK) and I want to make use of it by using it to allow me to connect to a server at my house. This all works fine for normal http (on port 80) but I have a music server running on port 9000 and no matter how hard I try I cannot connect to this port. I've setup my router to forward requests on port 9000 to the machine (this works ok for http on port 80) but I still can't get to it. Internally, it works fine. Force 9 say nothing it blocked at their end.

My router is a D-link DI-624+ (

http://www.dlink.co.uk/pages/products/129.htm)

with a DSL-300G modem (

http://www.dlink.co.uk/pages/products/136.htm).

Anyone any ideas?

TIA.

 

[manarth]

perhaps try running the music server on a different port: 21 (ftp) is so common that it's unlikely to be blocked.

it's not uncommon for an ISP's technical helpdesk to be unaware of currently blocked ports!

if it's streaming music, it's probably using UDP instead of (or in addition to) TCP, so make sure this is forwarded as well.

to test for this, you may want to try putting it in the DMZ (temporarily): if it works, then your next goal is to try and identify the other ports in use. If your music server runs windows, the command 'netstat' will show you a list of all active IP connections, the protocol (TCP/UDP), and the port number. you should try to identify which ones are specific to the music server.

when you've found the other ports you need, do remember to take the server out of the DMZ - otherwise you lose the security of NAT.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[tom1681]

Thanks for your response.

I forgot to mention that I've already tried putting the server in the DMZ and it made no difference (normal http requests were ok, the music thing not).

I've also tried having the router do both TCP and UDP which also didn't help.

FYI The server is running RH Linux 9.

I had thought of running the server on a different port (83 works for example) but soon I'll be getting a standalone device which connects via our wireless network to the device and I'm not sure (yet) if you can change the port that that connects to.

Is the most likely explanation that the port is infact blocked at the ISP then?

http://www.slimdevices.com/

is where all this stuff is coming from!

 

[bcastner]

The most likely eplanation is a firmware problem with your router.

Try to keep the port to be forwarded < 1025

 

[tom1681]

Interesting. D'you know of an upcoming firmware update for this router then? I have the latest one from the D-link website already.

Cheers

 

[manarth]

Another trick:
can your d-link's port forwarding specify forward from port A to a different port b?

e.g from port 88 to port 9000 ip 192.168.x.x?

This may help; both if your ISP is blocking ports and possibly with a firmware issue.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[bcastner]

Tom,

I do not know, but this Forum would -- it is monitored by D-Link Tech Support:

http://www.broadbandreports.com/forum/dlink

 

[manarth]

as another thought: could it be an issue with RH?
is it possible that it's configured to only accept connections from a limited range of IPs?

I run a range of services on a debian machine, and half of them are restricted to internal IPs.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[tom1681]

Thanks for the responses. I had tried forwarding from a different public port than the private port but this didn't help. I tried running the server on many different ports last night (all below 1024) and I could only get through on port 80. My ISP are still saying no ports are blocked (I asked again, I think they're getting annoyed with me now!)

My RH Linux is running it's standard firewall but as far as I can see all standard ports are open (and 9000 which the music server software added for me) and I can't see any mention of limited IP addresses - although I will try it tonight with the firewall turned off.

I'll also pop along to that forum and see what people say there about it being a router issue.

Cheers

 

[manarth]

Try running your apache server on port 9000.

(you'll hopefully find the config in /etc/apache/httpd.conf)
[ul][li]look for the line that says 'Listen 80': add a line beneath saying 'Listen 9000'.[/li][li]restart apache ([tt]/etc/init.d/apache restart[/tt])[/li][/ul]
If this doesn't work, it's a tossup between blocked ports or dodgy firmware: the only way to resolve it is to try with a known working router.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[tom1681]

Thanks for your suggestion but before I tried I thought of something else.

The Di-624 has pre configured rules (for http, https ftp etc.) and instead of adding my own to the list, I edited the http one to port 9000 and this worked! I can only assume from this that there is a bug in the firmware where user added rules aren't taken into account.

Thanks for all your help anyway.

Cheers,

Tom