Hi all,
First post here so firstly, hey! Hope all is well. I've recently (after many years of the standard ISP router) upgraded to an rt-ac68u. I love the tweakability and the vpn capabilities. Everything is working fine, apart from one thing - my dropbox desktop client. It appears the desktop client is just not being allowed through the router to communicate with dropbox.
Unfortunately, a search for a solution brings up many posts referencing the AICloud, but AICloud is for usb connected devices - i'm trying to sync my dropbox folders that are on my computer.
Dropbox seems to use specific ports according to the sparce information they give out (port 80, port 443 etc) and i've included these in the port forwarding section of the router, with a static LAN IP address that points to my computer (at least, i hope i've done that - by all means correct me if the following is wrong, or if there is something else I need to do to open ports). Under 'virtual server/port forwarding' within the WAN section of the asus router I have therefore put:
Port 80 - my IP - Protocol of 'both'
Port 443 - my IP - Protocol of 'both'
Port 17500 - my IP - Protocol of 'both'
Port 17600 - my IP - Protocol of 'both'
Port 17603 - my IP - Protocol of 'both'
Overall, i'm a bit unsure if this is correct, and i'm a tad unsure of the protocol for each i.e. TCP, UDP, BOTH, or OTHER. The only information i can really find from dropbox is this: https://www.dropbox.com/en/help/23
The other issue I did think it could be is the firewall within the router, but turning it off made no difference. I do see that the firewall has options to 'whitelist' things but again, that shouldn't matter as when the firewall is turned off, the dropbox connection issue still occurs.
To finish, I'm currently typing this using a wired connecting directly into my modem, and my dropbox is syncing fine so there's something in the router thats just not 'open'. I've zero'd in on port forwarding as the cause but i could be completely wrong...who knows! Could it be something completely unrelated to port forwarding and the firewall?
If anybody could help with this, i'd be so grateful - its driving me nuts!
Many thanks,
Ross
First post here so firstly, hey! Hope all is well. I've recently (after many years of the standard ISP router) upgraded to an rt-ac68u. I love the tweakability and the vpn capabilities. Everything is working fine, apart from one thing - my dropbox desktop client. It appears the desktop client is just not being allowed through the router to communicate with dropbox.
Unfortunately, a search for a solution brings up many posts referencing the AICloud, but AICloud is for usb connected devices - i'm trying to sync my dropbox folders that are on my computer.
Dropbox seems to use specific ports according to the sparce information they give out (port 80, port 443 etc) and i've included these in the port forwarding section of the router, with a static LAN IP address that points to my computer (at least, i hope i've done that - by all means correct me if the following is wrong, or if there is something else I need to do to open ports). Under 'virtual server/port forwarding' within the WAN section of the asus router I have therefore put:
Port 80 - my IP - Protocol of 'both'
Port 443 - my IP - Protocol of 'both'
Port 17500 - my IP - Protocol of 'both'
Port 17600 - my IP - Protocol of 'both'
Port 17603 - my IP - Protocol of 'both'
Overall, i'm a bit unsure if this is correct, and i'm a tad unsure of the protocol for each i.e. TCP, UDP, BOTH, or OTHER. The only information i can really find from dropbox is this: https://www.dropbox.com/en/help/23
The other issue I did think it could be is the firewall within the router, but turning it off made no difference. I do see that the firewall has options to 'whitelist' things but again, that shouldn't matter as when the firewall is turned off, the dropbox connection issue still occurs.
To finish, I'm currently typing this using a wired connecting directly into my modem, and my dropbox is syncing fine so there's something in the router thats just not 'open'. I've zero'd in on port forwarding as the cause but i could be completely wrong...who knows! Could it be something completely unrelated to port forwarding and the firewall?
If anybody could help with this, i'd be so grateful - its driving me nuts!
Many thanks,
Ross
Last edited: