DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
Connection on port 80
- afterdark
- Topic Author
- Offline
- Banned
Less
More
- Posts: 14
- Thank you received: 0
27 Aug 2013 08:18 #77536
by afterdark
Connection on port 80 was created by afterdark
Hi. I have just upgraded to fibre and have a new 2920n router inside the BT modem which the engineer installed. I run a 2003 SBS server and everything is working fine except for one thing.
I have set up the port redirection for smtp, http and https (ports 25,80 and 443) to the server and all my mail is coming in OK but I cannot access Exchange remotely anymore. It always used to work and I can still do it from inside the network (http://ip_address_of_server/exchange) but I can't do it from either my phone or from a remote PC.
I have tried changing the Management Ports for http and https to something other than 80 and 443 and also disabling internet management access but no luck. I have come across this sort of problem with other routers in the past but not with Draytek.
Apart from the basic wan, lan and port redirection settings, the router is pretty much straight out of the box. Can anyone suggest an answer?
Thanks.
I have set up the port redirection for smtp, http and https (ports 25,80 and 443) to the server and all my mail is coming in OK but I cannot access Exchange remotely anymore. It always used to work and I can still do it from inside the network (http://ip_address_of_server/exchange) but I can't do it from either my phone or from a remote PC.
I have tried changing the Management Ports for http and https to something other than 80 and 443 and also disabling internet management access but no luck. I have come across this sort of problem with other routers in the past but not with Draytek.
Apart from the basic wan, lan and port redirection settings, the router is pretty much straight out of the box. Can anyone suggest an answer?
Thanks.
Please Log in or Create an account to join the conversation.
- weehappypixie
- Offline
- Member
Less
More
- Posts: 117
- Thank you received: 0
27 Aug 2013 11:38 #77539
by weehappypixie
Replied by weehappypixie on topic Re: Connection on port 80
You need to change the routers default ports under management to say 8080 and 8443 in order to release the ports for rule use. Also, depending on the firmware you will also need to change change the port used for SSL from 443 to say 444.
John
John
Please Log in or Create an account to join the conversation.
- afterdark
- Topic Author
- Offline
- Banned
Less
More
- Posts: 14
- Thank you received: 0
27 Aug 2013 12:25 #77541
by afterdark
Thank you John. However, I have tried this - set them to 8080 and 8443 - but http traffic is still not getting through. As far as I know, the SSL port for Outlook Anywhere must be 443 but regardless, I still can't see the server on port 80.
Tim
Replied by afterdark on topic Re: Connection on port 80
You need to change the routers default ports under management to say 8080 and 8443 in order to release the ports for rule use. Also, depending on the firmware you will also need to change change the port used for SSL from 443 to say 444.WeeHappyPixie wrote:
John
Thank you John. However, I have tried this - set them to 8080 and 8443 - but http traffic is still not getting through. As far as I know, the SSL port for Outlook Anywhere must be 443 but regardless, I still can't see the server on port 80.
Tim
Please Log in or Create an account to join the conversation.
- weehappypixie
- Offline
- Member
Less
More
- Posts: 117
- Thank you received: 0
27 Aug 2013 16:22 #77546
by weehappypixie
Replied by weehappypixie on topic Re: Connection on port 80
It should work OK if you have the ports configured in NAT > Open Ports and create a rule to forward port 80, 443 and 25 to the local IP of your server.
Did you follow
http://www.draytek.co.uk/support/kb_vigor_portforwarding.html
Try opening Google and search for what's my IP to get your public Ip then try and connect tohttps://publicip/
Exchange normally uses HTTPS which is 443 and for that to work the management port must be changed.
Since your using SBS then IIS should listen to port 80 and then auto bounce you to the https: secure site on 443.
What does the DrayTek logs show?
John
Did you follow
Try opening Google and search for what's my IP to get your public Ip then try and connect to
Exchange normally uses HTTPS which is 443 and for that to work the management port must be changed.
Since your using SBS then IIS should listen to port 80 and then auto bounce you to the https: secure site on 443.
What does the DrayTek logs show?
John
Please Log in or Create an account to join the conversation.
- afterdark
- Topic Author
- Offline
- Banned
Less
More
- Posts: 14
- Thank you received: 0
28 Aug 2013 03:36 #77547
by afterdark
Replied by afterdark on topic Re: Connection on port 80
I think I have narrowed down the problem and of course it is associated with something I didn't mention before!
Right now everything works perfectly. I have changed the management ports for http, https and ftp and can connect locally to the router on port 8080. I have port redirection on ports 25, 80 and 443 to my server and I collect mail and can connect remotely to Exchange. I also have an ftp server on a different PC and have added a port forwarding to that and I can connect from outside the network. So, everything perfect? No.
What I also have is multiple public IP addresses. For the sake of argument, the block of addresses are 200.200.200.1 to 200.200.200.6. 200.200.200.1 is allocated to the modem and my main network, on which is the SBS server, is 200.200.200.2. I have set this in WAN > Internet Access > WAN1 using PPPoE and then set my local subnet under LAN > General Setup > LAN1. Using these settings, everything, including the port redirection, works.
However, I have a number of web servers which are on the other public IP addresses. In order to handle these, I have set the LAN > General Setup > IP Routed Subnet and used 200.200.200.1 as the IP address. Each web server then uses the relevant public IP address and has 200.200.200.1 as it's gateway. (Actually there are firewalls in between but ignore these for now). If I enable the IP Routed Subnet, then from the outside world, all my web servers can be accessed and my mail arrives.
Only problem is that now the port forwarding for http, https and ftp stops working but the smtp forwarding on port 25 still works. It is as though with IP Routed Subnet disabled, the Management Port Setup sees my user defined ports correctly but as soon as I enable the IP Routed Subnet, the Management Port Setup sees only the default ports and ignores the port forwarding on these ports. But because port 25 isn't part of the Management Port Setup, it is uneffected.
It may be that I am configuring the router all wrong for these public IP addresses and the Management Port Setup is a red herring?
Thanks. Tim.
Right now everything works perfectly. I have changed the management ports for http, https and ftp and can connect locally to the router on port 8080. I have port redirection on ports 25, 80 and 443 to my server and I collect mail and can connect remotely to Exchange. I also have an ftp server on a different PC and have added a port forwarding to that and I can connect from outside the network. So, everything perfect? No.
What I also have is multiple public IP addresses. For the sake of argument, the block of addresses are 200.200.200.1 to 200.200.200.6. 200.200.200.1 is allocated to the modem and my main network, on which is the SBS server, is 200.200.200.2. I have set this in WAN > Internet Access > WAN1 using PPPoE and then set my local subnet under LAN > General Setup > LAN1. Using these settings, everything, including the port redirection, works.
However, I have a number of web servers which are on the other public IP addresses. In order to handle these, I have set the LAN > General Setup > IP Routed Subnet and used 200.200.200.1 as the IP address. Each web server then uses the relevant public IP address and has 200.200.200.1 as it's gateway. (Actually there are firewalls in between but ignore these for now). If I enable the IP Routed Subnet, then from the outside world, all my web servers can be accessed and my mail arrives.
Only problem is that now the port forwarding for http, https and ftp stops working but the smtp forwarding on port 25 still works. It is as though with IP Routed Subnet disabled, the Management Port Setup sees my user defined ports correctly but as soon as I enable the IP Routed Subnet, the Management Port Setup sees only the default ports and ignores the port forwarding on these ports. But because port 25 isn't part of the Management Port Setup, it is uneffected.
It may be that I am configuring the router all wrong for these public IP addresses and the Management Port Setup is a red herring?
Thanks. Tim.
Please Log in or Create an account to join the conversation.
- frag
- Offline
- Member
Less
More
- Posts: 115
- Thank you received: 0
29 Aug 2013 17:28 #77555
by frag
Replied by frag on topic Re: Connection on port 80
hello,
make sure that the WAN IP address and the IP routed address differ. You should then be able to configure the NAT rules normally.
make sure that the WAN IP address and the IP routed address differ. You should then be able to configure the NAT rules normally.
Please Log in or Create an account to join the conversation.
Moderators: Sami
Copyright © 2024 DrayTek