Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mackconsult]

This is weird. 

Since January I have had a QNAP TS209 running my blog from closet in my house.  Its comcast and the DIR 655 has worked flawlessly letting me get web page access (forwarding threw godaddy.com), FTP access, and telnet access to my server using port forwarding.

Last week I updated my NAS with some plugins and something broke.  So I uninstalled the plugins and now the NAS can be accessed from my home and out on the internet no problem.  Still broken at work though .....  I even called godaddy.com because I thought maybe something was broken when accessing the URL, but they were able to access my website no problem.

Ref:  http://www.mackconsult.com/

When I try to access the website at work I get the following:

*********************
Network Error (tcp_error)

A communication error occurred: "Operation timed out"
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

For assistance, contact your network support team.
*********************

Also FTP and telnet don't work at my work either ....

I wouldn't think it is a problem with DIR but posting this here and at the QNAP forum to solicit input.

[EddieZ]

Website works fine.

Check your company proxy setting 

[mackconsult]

Thanks.  I use Mozilla and internet explorer at work.  I think the proxy settings are okay because I can access every other website except mine in both of these browsers 

[EddieZ]

It's not the browser proxy I am talking about. I assume that your company might have a proxy running. If not (and you all have unlimited access) this does not fly ofcourse. I cannot see any local issues, besides maybe your NAS has excluded your work IP. But that's about the most I can make from this.

[mackconsult]

Thanks.  I am at a loss at this point as to what has happened.  Web, configuration, FTP, & telnet all don't work from my place of work, but will work every were else.

What is interesting is that ping reply is turned on on my Dlink and still can't ping it from work.

I did more research and found that my domain (www.mackconsult.com) maps to 64.202.189.170 which then forwards to my dlink IP of 24.22.111.116.

When I ping the 64.202.xxx.xxx from work in a command window there is no reply.  Same with 24.22.xxx.xxx.

But if I go to http://ip-lookup.net/index.php and plug in these IP's I get a ping reply.  So it must be my work that is filtering my access.

[mackconsult]

Just keeping this thread alive.  I did some more testing.

Last night I reset my dir 655 completely.  Enabled ping and then VPNed from home on my laptop to work.  Was still not able to ping my router directly through a shell on this VPN.  Even though I could access a website threw that VPN that did ping my router just fine.  Reinstalled all my settings on the router to get it back to normal.

Then at work this morning I tried another computer on the work network and still the issue is there.

I have given up on this issue .... not sure what the problem is but I think it must have something to do with my network/DNS configurations here at work.

[marmoduke]

do a ipconfig /flushdns and start fresh. 

[tipstir]

I just tested it and there was a delay to get to your site but I finally got in.

What hardware version and firmware version are you using?
What ports are you using for remote access?
You're just running the QNAP Web/FTP server hardware only?

[smlunatick]

So, this is the set up:

Web --> 64.xx.xx.xx  forwarding to 24.yy.yy.yy (D-Link) then forwarding to the internal QNAP NAS?

If this is the case, check to see if the port forwarding is correctly set.  The QNAP unit should be either using a STATIC IP address or IP reservation.  Then, the D-Link should have a correct "virtual server" port forwarding to the QNAP.

[mackconsult]

Still does it

do a ipconfig /flushdns and start fresh. 

[mackconsult]

It is a TS209 so does not have a lot of resources on board.  It's the SQL queries that bring it to its knees.

for web port 80
telnet port 23
ftp port 21

I will edit this post once I get home for
hardware not sure
firmware versions 1.32NA,  2009/07/09

I just tested it and there was a delay to get to your site but I finally got in.

What hardware version and firmware version are you using?
What ports are you using for remote access?
You're just running the QNAP Web/FTP server hardware only?

[mackconsult]

Yes its setup as you show below

Qnap has always been static.  If one goes outside my company firewall everything works fine.  Its just when I am behind my companies fire wall that it does this.

So, this is the set up:

Web --> 64.xx.xx.xx  forwarding to 24.yy.yy.yy (D-Link) then forwarding to the internal QNAP NAS?

If this is the case, check to see if the port forwarding is correctly set.  The QNAP unit should be either using a STATIC IP address or IP reservation.  Then, the D-Link should have a correct "virtual server" port forwarding to the QNAP.

[davevt31]

Then your company is doing the blocking.  You will need to talk to them, but I would imagine its to keep their information more secure.

[mackconsult]

"talk to them" yaeh right, no way that is going to happen ....

Whats weird is that I was able to access it from Jan all the way till Sept.  Did some plugin updates on wordpress and it broke it .....

I give up .... at least every one else on the internet can still access it, I just can't update it at work any more.

Back to the grind.