Port forward with Orcon not working

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Port forward with Orcon not working

billytf

8 posts

Wannabe Geek

#80232 29-Mar-2011 08:44

Hi, I'm having problems with getting port forwarding to work with my new Orcon connection. I've got the standard 5Gb plan, single port Netcomm modem from Orcon and that's connected to a D-Link wireless router.

I've ruled out the router by just using the Netcomm (direct connection from PC) but when I setup a port under virtual servers (services maybe?) and use canyouseeme.org it either says it has timed out or it's blocked.

Orcon has assured me they do not block any ports (I've tried multiple options in the 40000-60000 range) but have stated it's not something they support.

I'm also pretty sure I know what I'm doing and the on-line guides confirm I'm setting up the modem/router correctly. Windows firewall is off and I've tried turning the modem/router firewalls off too.

I had this working at my previous residence where I used a TCL cable connection.

Can anyone help or tell me how to get a good download speed (torrents mostly) without this?

Thanks

bazzer

3438 posts

Uber Geek

Trusted

#453030 29-Mar-2011 09:04

I don't have any problem forwarding ports with Orcon (although I use a different modem/router), so I don't think they are blocking. It must be a problem with your setup. Maybe post a pic of your port forwarding settings?

Another thing you could try is putting your machine in the DMZ temporarily? That will let you rule out your PC as the problem I guess.

Sounddude

I fix stuff!
1928 posts

Uber Geek

Trusted

2degrees

Lifetime subscriber

#453046 29-Mar-2011 09:55

We DO NOT block ports. It sounds like an issue with the modem itself not forwarding the ports though.

billytf

8 posts

Wannabe Geek

#453082 29-Mar-2011 11:13

Hadn't thought of using the DMZ so will try that.

Sounddude, I was told you didn't, wasn't suggesting otherwise

I do have some weird connection issues with the modem, it only starts up with the line in isolation and when connected directly to a PC or a standard port on the router - not a pass-through port. Any other setup and it fails to connect. An oddity that may be something to do with my line but not an issue (unless it's causing other problems that I'm not aware of yet)...

billytf

8 posts

Wannabe Geek

#453574 30-Mar-2011 19:00

OK. Tried this:

Connected machine directly to the Netcomm modem. Disabled local firewall and other security software. Setup DMZ on Netcomm to use the computer's address and also even added port forwarding for all ports. canyouseeme.org is now saying for any port that I try 'connectiopn refused'.

Any ideas?

Thanks

bazzer

3438 posts

Uber Geek

Trusted

#453736 31-Mar-2011 10:24

The likely possibility is that you have set something up wrong. If you're using DMZ, there's no point having any port forwarding set up as it's irrelevant.

billytf

8 posts

Wannabe Geek

#453750 31-Mar-2011 11:08

Any idea how I can diagnose where the problem might be? I setup port forwarding only after DMZ setup, i didn't think it was relevant but I wanted to rule it out.

I set DMZ to the computer's local address (which is still on 192.168.x.x).
Disabled Windows firewall.
Disabled Norton security.
Disabled Netcomm firewall and SPI.

Where next?

Thanks

bazzer

3438 posts

Uber Geek

Trusted

#453752 31-Mar-2011 11:12

I guess you need to figure out what's blocking it. We know it's not Orcon (I don't know if a problem on their side could cause this), so that leaves the modem or the PC. I guess you have to isolate it to one of those. How? Do you have another modem you could borrow that you know works? Ditto for the PC? Otherwise, I don't know. You say you've turned off firewalls etc, can you check logs for blocked messages?

Sharesies kids

Free kids accounts - trade shares and funds (NZ, US) with Sharesies (affiliate link).

billytf

8 posts

Wannabe Geek

#453757 31-Mar-2011 11:26

Have another machine so will rule that out. Might be able to borrow a modem so shall see and let you know.

Ta

billytf

8 posts

Wannabe Geek

#453895 31-Mar-2011 18:33

OK. Problem solved. It seems Netcomm's SPI 'firewall technology' was causing the problem. (I had disabled this previously but only when trying the DMZ mode - which I can't get to work but don't need to now.) So, there might have been two issues originally, now I only have one which I don't care about.

Actually, that's not true, it seems when my BitTorrent client starts up all http traffic stops; but that's for another conversation which I'll post in another thread.

Thanks for keeping me sane!