News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

Nas not visible externally

Started by drac, August 04, 2009, 12:51:37 PM

Previous topic - Next topic

drac

   

My first NAS.  LS-WTGL495 / LS-WTGL/R1-V3 F/W 3.08.  Linksys router WRT54G with 1 wired PC and 3 wireless PCs.  Plus the NAS of course.

 

I have this NAS up and working internally, but I can't find it from an outside connection.  Fron the network Buffalonas.com/neetconas connects and works fine.  But the same URL outside "Timed Out". I've tried this withauto-gonfig and also Port Forwarding.  I feel like it just my inexperience, so any help is apreciated.


JoshC

You need to open up port 9000 on your router.  Turn off auto config.

drac

   Took me a while to return.  Still no luck.  My port scanner says port 9000 is open. The Web Access Service Setup Auto Config is set to enable. When I go to "Buffalonas.com" and enter my NAS name, I am sent to my routers IP & port 9000 okay.  But if I try that from another location away from the office, it does not work.  I just don't know why.

packdog

   

http://forums.buffalotech.com/buffalo/board/message?board.id=0101&thread.id=13494&view=by_date_ascending&page=2

 

I'm having the same issue. Play with canyouseeme.org and see if you get what I've got (i posted it in the above link, 4th post on 2nd page).  My thought is that it's a permissions access issue with the NAS. ie. the nas looks to see who is logging in, and rather than post a login screen, it simply refuses the connection from the internet. it's a real bummer.

Message Edited by packdog on 08-12-2009 02:43 PM

drac

   

I am about to give up.  I can not get Web Access to work on my new Linkstation Duo Pro.  The site http://www.canyouseeme.org/ says port 9000 can NOT be seen from the internet.  On my router, port 9000 is set to open AND the NAS is set to autoconfig, which should use 9000 anyway. and that I verified using a post scanner on my computer inhouse.  Using Buffalonas.com/"our NAS name" returns our IP with ":9000" after it.  I don't understand how this can be.

 

As a seperate question, if I enter the URL of my IP with :9000 should that also go the the NAS?


packdog

   

It won't necessarily use WAN port 9000 if it's set up to auto config (UPnP). when you log into the NAS admin there will be box that is greyed out stating which port the NAS is going to use to access the internet. in UPnP mine went for 45744. my point is that it's most likely not going to be 9000. the NAS uses 9000 within your LAN and that is non-configurable.

 

Personally, uncheck the UPnP and static the port to 9000. I believe this to be more reliable. but then again, i can't get mine to work either, so i may be wrong too.

Message Edited by packdog on 08-13-2009 02:24 PM

Benta

   

I also had similar problems. I checked the log of the router and realized that it is UPnP on the router that isn't as stable as it should be, so if you have problems with it, try turning it off in both the router and the NAS.

 

Then pick an IP number in the range of your lan (say 192.168.1.80 if your router gives out numbers in the range of 192. 168. 1. 1-100) and tell the linkstation to always use that number (i.e. "static IP" rather than get from DHCP).

 

Then look in the web interface of the NAS to see which external port number it will be using. You can set this number to whatever you want (it is 14000-something by default). Let's say you pick port N.

 

MAKE SURE THIS PORT NUMBER IS  NOT CONFLICTING WITH OTHER DEVICES ON THE NETWORK!!! It did in my case.

 

Then configure your router to forward the external port N to internal IP: 192 . 168 .1 . 80 :9000 - because the LInkstation always uses 9000 internally.You can't change this (and you don't need to)

 

 

I just started looking around here, and many problems that people post seem to be related to difficulties with router setup....

 

 


james557

   When setting up Web access, if you are going to open port 9000 DO NOT keep the linkstation on auto config firewall. It will not use 9000. You have to actually use the setting "use external port blank" and type in 9000. Also if you're seeing that it's opened on your router but it cannot be seen from the internet that means that your modem or ISP is blocking that port. I would recommend checking with your ISP if they have any port restrictions on that port and have them open it up if so. I know that a lot will do that for tightened security and preventing illegal file transferring (i.e. movie and music sharing). That works with most of my customers. If not let me know, I have replies on this post email me the responses so I will get it shortly after you respond.

drac

   

I just talked w/ Comcast, our ISP.  That is a long story, but I did end up talking to an intelligent person who satisfied me that port 9000 is not blocked.  I've double checked the items you listed (auto-config disabled, port 9000 entered, 9000 active on router).

 

Everything seems right to me (a novice) and I am at a loss as to how to fix this problem.  HELP!


Benta

   

Have you configured your router?

 

 


drac

   

To the best of my knowledge, yes.  By configure, I mean open port 9000 to the NAS at 192.168.1.104.  What else is there?

 

 


Benta

   

So port 9000 from the outside is forwarded to port 9000 on the inside?

 

If you go to www. buffalonas. org/yourserver when you sit inside in your home on your home network, does the browser get you to the server?

 

 


drac

   

Yes, regarding the 9000.

 

In my home network, which is my office,www.Buffalonas.org/my server does get me to my NAS onthis home network.  The URL reads 192.168.1.104:9000/

 


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 338 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1102KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]