Can't access Diskstation from Work

[saicrazyfire]

Hi all,

I have Synology DS211 with Apache running on port 80. I have properly forwarded the ports on my router so that I can access the server from outside my network. I can verify this works because I'm able to connect from school and from my phone (3g/4g).

My issue is that I can't connect to my server from my workplace. The network guy in my office is okay with my accessing my server (it's just a webserver) but hasn't been too helpful on figuring out why I can't connect to my server. I can't even ping my router!

I was wondering if it might be due to my server not having an SSL certificate? If so, do I create the SSL cert on the diskstation? What about the router? My DynDns url is hitting the router not the Diskstation so shouldn't my router have the SSL cert installed? If this is not the case, what can be some causes and how would I be able to work around that?

Thanks in advance!

[axj]

I think, it could be some port on your router, which is not re-directed correct!
Also see/ask for blocked port at your work-place!

[saicrazyfire]

Yep, I tried that. He gave me a port that is unblocked but still no luck

[axj]

Did you try using a standard protocol (not SSL)?

[saicrazyfire]

Well I don't access Apache over SSL if that's what you mean. My WebDAV is SSL only for now but I'd rather worry about accessing Apache over the network (WebDAV also doesn't work). I feel like it's my network at home. I can't ping/tracert my router ip.

Thanks for your help.

[axj]

I thought, it was easier to detect the problem(s) if not using SSL!!
You may know the princip KISS!!

[grao]

I have this exact same problem. I can connect to my server with my iPad if I tether it to my phone. I can connect from outside work. I can connect to my webcam with a host redirect from work (using a forwarded port). But I cannot connect from work. I keep getting am error (that maybe coming from my work server). I don't get why I can connect to my webcam, though, and not my NAS. They have the same external IP but a different port. This makes me wonder if something is set up incorrectly with the NAS Firewall.

[saicrazyfire]

Well I have already disabled SSL for Apache. I'll disable SSL for webdav but I don't see how that would impact anything since I'm not trying to access WebDAV. I'll have to try again when I get back to work.

I even tried accessing SSH over the corporate network and no luck. I don't understand why I can SSH into other boxes but not to mine. What are some possible issues that can cause this?

[axj]

What about the ip-blocking list? (NAS or router?)

[grao]

I found a solution to my problem at least. Turns out, the IT guys at work have the firewall set toblock certain ports (synology uses 5000 by default). I picked another one at random in the DSM settings (control panel), and it isn't blocked so now I can access the NAS from work. Try picking a high one (like in the 30000 range) and see.

[saicrazyfire]

Hmm...that's interesting. I will definitely try that, thanks. Have you tried accessing your synology's website (by that I mean the Apache server, if it is enabled)?

@axj
No, that's the first thing I checked. No IPs are blocked.

[saicrazyfire]

I tried port 30000 and that still didn't work. Any more suggestions?

[LastChanc]

After reading this thread I'm curious, what is the exact error you are encountering when trying to access your home ip from the work place?

From what you've said you can successfully access the web service from both inside and outside of your LAN, however the only place you have an issue is at work which suggests your port forwarding and local configuration are fine and the problem is something such as a proxy which is causing you trouble.

I often have trouble with the gateway at work - and in the case of my box will allow me to connect to web service but won't allow me to access other ports such as the admin login, I'm wondering if you're experiencing something similar or can you not access anything at all?

Regards,

Darren

[saicrazyfire]

There's no error message per se, but I just can't connect to my server. Its the standard error when a browser tries to talk to a server that doesn't exist. I had a feeling it must be the proxy at work because I can't ping my router or even see it. I did a tracert and everything just times out.

I find this weird because I was able to successfully SSH into another box for work...What makes his machine different from mine?

[LastChanc]

The ping I would expect to fail unless you've played with your configuration as most home routers AFAIK are set to ignore ping requests coming in from the wan interface, at least in my experience.

At what point did the tracert fail? Did it make it out of the company? Did you see your ISP? Again if you're not replying to ping on the wan port it will not complete as it cannot get a reply from your router which is the end destination.

If it is down to some kind of firewall/proxy in place by your company (either at your location or perhaps in a headoffice or such like) then they may just block a lot of sites purely by default until they make an exception in the rule.

Regards,

Darren