Problems setting up Linksys/DLink network

[tickytacky88]

I have a DLink DIR628 wirless router on cable internet. I recently purchased the Linksys NSLU2 NAS device. When I put the disc in for the linksys device to set it up it cannot find the device attached on my network. The computer I am setting it up with is hardwired, i tried a wireless one, i have WEP security and i have already power cycled everything a few times thinking that might be the problem. any help would be much appreciated I leave for a few months soon and need the NAS set up ASAP. THANKS!

[+BudMan MVC]

And what lights do you get on the device? Does the network light show that is has a link? its not beeping at you is it?

You should be plugged into your routers lan port with the PC your going to configure the thing for the first time with. And the nslu2 should also be plugged into a lan port on your router. Connect it to your router and then apply power to it. It can take a few minutes to boot up.

Once your sure its booted up, and your network light is good, then try to find it. It has NOTHING to do with your wireless network. But it could be an issue with a wireless machine trying to find it on the wired network.

You do not have any any outer devices or router in any type of daisy chain where the devices could be on different segments or behind a nat.. Ie you don't have any VOIP devices, etc. do you?

[tickytacky88]

On the Linksys device the power light is solid green the ethernet light is solid green and disk 2 is solid green. the computer i am setting it up with is hardwired to the router just like the linksys device. i dont have anything on the router other then there two and three wireless laptops, no tivos, voip or anything. it does not beep however, when i turn it off then on it makes one beep when the lights change from orange and blinking to solid green.

[+BudMan MVC]

You are running the setuputility.exe first and not the install util?

I think the default IP of the device is 192.168.1.77/8

What network is your machine on? I would suggest you try putting it on the 192.168.1.0/8 (255.0.0.0) and see if you can find it then. Or see if you can access the web gui with the 192.168.1.77 address

Make your machine something like 192.168.1.99 255.0.0.0

[tickytacky88]

ok so after changing my ip and subnet mask i can access the linksys web controls. i formatted the drive. it looks like its good to go. however, since i changed my ip and subnet i cant get online and i dont know how to set up the device correctly so I can access the files on it from the web. how do i do that and what settings should i have all around?

[+BudMan MVC]

Well, I would suggest you change your PC ip back to your normal routers network, dhcp I would guess after you change the nslu2 IP to be on that network -- something outside your dhcp scope.

As to how to access it from outside your router. Does the native firmware support http or ftp acces to the shared drives?

If not you could put unslung or slugOS on it. http://www.nslu2-linux.org/ I know there are quite a few packages you can run to allow for http or ftp access to it.

Depending on what your using to access the files of the device, would determine which ports you need to forward on your router to the devices IP.

[tickytacky88]

yeah i honestly have no idea i am very new to this

[+BudMan MVC]

Well if you just using windows file shares, ie SMB/CIFS -- samba, whatever you want to call it.. Your not going to be able to access that from across the public net. You would have to vpn, or ssh tunnel into your network to for that.

I'll take a look at the devices native firmware to see what modes of access to the files it supports.

if you knew you were going to need to access its files from the internet. Why did you not verify what it can do before you purchased it?

[Volatile]

** Similar to budman but holding your hand...

I've setup one of these devices... and its just giving the device a static IP in conjunction with your network. If you don't know it or how to look for it, make sure your computer is hooked up to your dlink router and that you can access the web. Just go to start/run and type in cmd. In the black rectangle type in ipconfig /all and you will see your wired LAN IP. Basically everything listed should be identical except you will need to change the IP. If your IP is currently 192.168.0.100, I would set the NAS to 192.168.0.200. You should then reboot the NAS so it can come back up. You should also have an option to name it so that you can access it by name versus IP. When all is said and done you just type in \\IP or hostname to get to the device.. or create a mapped share on your computer(s) accessing it. Make sure the Dlink doesnt have a firmware update as well. In my experience with Dlink.. a strange problem has always been solved by firmware.

[+BudMan MVC]

That is all fine and good but access the file shares off the machine \\nameyougaveit does not allow for access from the public net.

I do not see anywhere in the UG that makes any mention of ftp or http access to the files with the native firmware. So to be able to access files on that device, you are going to need either access to a machine that is on the same network it is with drives connected to it mapped, etc.

Or you going to need to be able to vpn/tunnel into your network -- be it hamachi, or some sshd or other solution that allows you to tunnel into your network, or access a machine that is on your home network and connected to the nslu2 shares.

Your best bet would be to put one of the many 3rd party firmwares on the device that will give you different methods of accessing the drives connected to it.. I already linked to where you can get info on this.

Or your going to need to return that device and get one that supports a method of access to the files better suited for access across the internet. Say ftp or http.

Are you going to have another computer running on your home network while your away from it? If so then sure we can work out multiple methods for you to get to the files on the nslu2. If not -- your going to need to install a different firmware on it, or return it - sorry.

edit: Its seems that the devices does support a ftp server.. Under the system tab from a few quick googles -- enable ftp on the device. The configure your router to forward 21 (ftp control port) to the IP you gave the device. You can find out how to do this on your router in its manual, or at www.portforward.com

edit2:

http://www.linksysinfo.org/forums/showthread.php?t=38650

Using the NSLU2 as an FTP server

Edited August 7, 2008 by BudMan

[tickytacky88]

So I have done everything and I think I am almost there. so far In firefox I can type ftp://myip and it shows an interface that looks like it access the drive. however, there is no files listed there, i tried plugging it into my laptop, cant access it, probably because of the formatting the linksys device did. how would i get files onto the drive now? via ftp?

[tickytacky88]

update: if i go to ftp://192.168.0.69 I can access the files i have been able to upload to it via the my network places feature in XP however it was very hard, froze a few times and is very slow. does anyone know how I can access these files from the web whenever i try ftp://external ip nothing is displayed

[+BudMan MVC]

Well for starters did you setup the port forward for ftp to the .69 address, or put that .69 into the dmz of your router?

Also -- its rare that you can hit the external address from the inside and get forward back in. That is a loopback forward and lots of router have issues with it. And to be honest its kind of a security issue -- you would not want your router sending traffic from the outside interface to the internal network if the source IP was an private address, etc.

Nor does it make any type of sense to bounce of your router to access box that is on the internal network.

To verify that it will work from the outside, your going to need to test from the outside.. As to being slow?? Don't use a browser to access a ftp site -- use a ftp client. filezilla, winscp, etc.

[tickytacky88]

good point. i will be testing it from the outside later today at a friends house. thanks for the info. in response to the ftp client, i cannot get any ftp client to connect, i have WSFTP pro, filezilla, none of which work?

[+BudMan MVC]

Well that's just nonsense - FTP is FTP is FTP.. Any ftp client can connect to any FTP server. I have no idea what your doing wrong.. But saying you can only get your browser to connect to your ftp server points to some bit of info your leaving out.

What account are you using? Anonymous? If I had to guess your putting in the wrong credentials - what error do you get from the ftp client? Are you using active or passive?

[tickytacky88]

i have a user name and password i put in the ftp address and click connect what info do you need? how should it be setup. i appreciate your taking time to help with this

[+BudMan MVC]

What error/codes does your ftp client give you when you say you can not connect. Your not putting in ftp:\\ipaddress as the site in the client?

in the ftp client it would just be the IP address.

[tickytacky88]

ok i tried using an ftp client on a different ip address and connecting to it via my external ip as the host and then user and password. it says connected but never recieves a welcome message using filezilla. i am able to use WSFTP and using the local ip 192.168.0.60 connect to it on my local network when i am home and transfer files, however, out of my local network I cannot connect. seems like i have a setting problem i just wish i knew where and what ??

[+BudMan MVC]

And did you forward port 21 on your router? Or put that nas ip into the dmz of your router?

[tickytacky88]

i have 192.168.0.69 with port 21 routed and open at all times, i have tried putting 192.168.0.69 into the DMZ option as well and it didn't allow me to connect. however, i am at a computer now on a network and when i ping my external IP it pings fine and gets a response.

[+BudMan MVC]

Ok in one post you say your connecting to the ftp server on 192.168.0.60 "i am able to use WSFTP and using the local ip 192.168.0.60 connect to it on my local network"

But then in another you say you have 21 forwarded to 192.168.0.69 "i have 192.168.0.69 with port 21 routed and open at all times"

Which one is it?? Sounds like port forward issue to me. WTF does pinging your external IP have to do with ftp being open??

[tickytacky88]

the local ip of the linksys device is 192.168.0.69 and port 21 is open i typo'ed before with the .60 sorry any ideas where i am going wrong with settings?

[+BudMan MVC]

And what is the model number of your modem? You sure its doing nat? Almost every single time a user has issues with port forwarding, its because they are behind a double nat.

Or its possible your ISP blocks inbound on 21? Please give the make and model number of your "cable" modem.

[tickytacky88]

i figured it out!!! finally, the problem was in the linksys device settings i have the anonomous requests box for ftp server checked, when i unchecked it everything works from external ip's via an ftp client in active mode. thanks for all the help!