Draytek 2860 Port 443 / SSL not working port forward

draytekThere seems to be a bug in the Draytek 2860 router, even though I had changed the management ports from the default 80 and 443 to 8080 and 8080. I was still unable to port forward any 443 traffic and would end up getting an 404 error page from the Draytek 2860.

The next thing I tried was to disable the SSL vpn in the remote/vpn section, this made a change as I now no longer got the 404 error page from the router while trying to browse to https://mail.mydomain.com but still the port forwarding was not working.

After drilling down deeper into the Draytek 2860 SSL VPN settings, I changed the port the SSL VPN uses from 443 to 44444. I did not think that this change would make a difference as the SSL VPN was disabled, I was wrong!  The 443 port forward started working, so even though the SSL VPN was disabled, it seems that port 443 was still in use by it.

I hope this post helps others!

TCPDUMP to sniff headers

This tcpdump command will grab the first 1024 bytes (vs. smaller 68 or so) and line buffer the output for all packets using port 80 (http)

tcpdump -s 1024 -l -A port 80

Check Nagios cfg files

nagios -v /etc/nagios/nagios.cfg

Subnet Mask Cheat Sheet

The below table shows the amount of hosts that are on a particular subnet.



Very handy for Office 2013 installs


Large BaditemLimit

When moving mailboxes from Exchange x to Exchange 2010 the bad item limit is set at max of 50, if you have a mailbox that has more bad items than that you can do the move request via the Exchange Management Shell using the below command


New-MoveRequest -Identity ‘Alias goes here’ -BadItemLimit 100 -AcceptLargeDataLoss


Change  the Alias goes here for the mailbox alias keeping the ‘ ‘ as an example if we were moving my mailbox we would enter ‘William Rendell’ Also change the 100 for what ever value you want to set for slipping bad items.


Add a static route in Smoothwall

ip route add via

Delete a nat rule in iptables

First of all I list all the rules including line numbers like this;

iptables -L -t nat –line-numbers

I then look at the output that will be similar to the below




In this example lets say I want to delete rule number 2 in the PREROUTING chain, I would enter the following;

iptables -t nat -D PREROUTING 2

In English the above line means remove line number 2 from the PREOUTING chain, I would then run the first command again to check my iptables file, then save the iptables file and restart the iptables service.

iptables -L -t nat –line-numbers

service iptables save

service iptables restart

All the above is carried out running on Centos, you may have to edit slightly for your particular distribution.

Don’t ever give up!

When you don’t give up,YOU CANNOT FAIL

Derek Redmond running in the 400m Olympic final in Barcelona 1992.

This is hard to watch without getting emotional………

Exchange 2003 database size

The database size limit for Exchange 2003 standard is 16GB, however SP2 for Exchange 2003 allows you to remove that limit. The default size for priv.edb after installing SP2 for Exchange 2003 is 18GB this can easily be changed for database sizes upto 75GB per database.

The steps below explain how to increase the 18GB limit by editing the registry. Edit the registry at your own risk, I will not accept any responsibility if you run into problems.

  1. On the Exchange 2003 server, run regedit
  2. Navigate to the following registry key

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID

  3.  Create a new DWORD entry called “Database Size Limit in GB”
  4.  Change from Hexidecimal to Decimal and enter the value of the size in GB that you wish the maximum DB size to be.
  5. Exit from the registry editor
  6. You should now either restart the Information Store or dismount and mount the store in question.

The maximum database size for the priv.edb should have now been increased to the value you set in the new DWORD