Printable View
I have just taken delivery of a new thecus 5200. it seems to be working fine except the lan light doesn't come on, although the wan light does. I have my modem router connected into the wan port and a pc connected to one of the lan ports. the pc cannot access the internet.
the lan light at the back where the cable is plugged in is on, the front panel lan light is off.
This is with firmware version 2.0.4
I didn't pay attention to that lights up to now, but it looks like the front lamp is blinking only if activity happens, while the lamp on the rear must be on as soon, as HW-connection to an Ethernet is there (the green lamp, yellow blinks also during activity).
To access your NAS, follow the instructions and find how to set up network-configuration. The delivered state uses an IP-Address that probably is not compatible to your environment. So you first would have to change the address of your PC according to the needs of the NAS and change that to your needs, than the PC back again.
There is also a point to configure the both LAN connections, in case you need different addresses. More common is probably, to bridge the to connections on the same address and use the NAS within one network, but this depends of course on what you need.
Oh, I just see that you want to use the NAS as a kind of router, prior to your Modem. I don't think that this will work, as you first would need a so called cross-over cable for the connection from PC to the NAS and than, somehow the WAN Plug must get a configuration to deal with the modem. Both connections are simple LAN connections, that means, your modem must be something like a router plus modem. I don't think, that you are able to get a software on the Thecus to handle a modem directly, but I am brand new to this devices also and maybe, I fail with that.
Normally, the NAS will become just one member within one network, what is your home network and all members are connected with switches and may be connected to a router, that connects to a different network, like Internet. You not have to “wire through” the NAS, it is wired parallel and handling of addresses and routing protocols do the rest.
I am not sure with that, but it looks to me, as if the WAN connection is just a choice to enable a more secure handling of incoming calls, so a use from the Internet or any other network to your NAS.
Hi thanks for your response. Let me explain the situation a bit better:
I have a modem-router with 4 ethernet ports and built in WiFi. That is all working fine.
One of the ethernet ports from the modem is going to the wan port on the n5200. With this configuration, everything works fine, the wan light on the front blinks.
However, if i connect a new pc to one of the lan ports on the n5200, it cannot see either the n5200 or any of the devices attached directly to the modem (even via ping), or get internet access. What's more is that even if i set the n5200 to provide dhcp to the lan ports, any attached pcs will not get a valid ip address. At no point has the lan light on the front become illuminated (except during the start-up test).
If I connect the pc to one of the sockets on the modem directly, it all connects fine.
From this I am beginning to think that maybe there is a fault with the n5200?
no, not as far as I understood its working.
That is just right.
Consider the 5200 not as a Bridge or router or something like that by default.
My one has only one LAN and one WAN Ethernet connection and both are "isolated" network cards that can be hooked up to different Networks.
The DHCP Server, if switched on in the NAS will serve the configured output with adresses, in the range configered for this output.
With other words: each LAN Port and the WAN port needs a proper configuration within the NAS and do not automatically belong to the same network(s).
So, what you tell is fully understandable and as it is thought to be.
I give you an example on how the 5200 is set up in my network:
I decided to "bridge" LAN and WAN connection, that was one point in the configuration via the webif. I decided this, because I want the NAS to only appear in one network, what is my home network and I just have only this one to deal with. So, I also needed only one IP-adress and can use both connectors, means, what ever one I want, but only one at a time.
This is connected to a switch. Your modem-router has one build in, that is why it can handle four ports. So you can use it and attach the NAS plus three other devices, each one with propper IP adress settings. Be aware, almost all routers do operate a build in DHCP server, you should not run two on the same network, so switch of either the one in the router or in the NAS.
Thats all.
Would you want to connect to more than one ofe the LAN-connectors on the NAS, you should set up a different Network with an own switch to connect those members, or you must use a cross over cable to connect one member directly to the NAS. But this will be a new network and is not visible from the other network, as long as you do not build a router between those networks. Thats true, even if you would like to use the same IP-Adresses as in the first network. The conectors are seperated in the NAS, there is no switch build in in it (at least not in mine).
Maybe, the NAS could work as such a router itself and thus, connect two (or in your case maybe even three) networks, but even if, this has to be configured and never will run automatically.
My advise for you: just only use one LAN port of your NAS and all is fine. I am not sure, how it was from the beginning, maybe for configuration you need the WAN, at least as long as you did not set this bridge funktion. In this case, you may want to just only use that port, doesn't matter, but only one that will be configured in your network.
Hope that helps.
i think so-- thank you
The RouStor edition of the 5200 has a built in switch. It is perfectly possible to do it.
Winter, when you connect the PC into the switch of the N5200, can you log into the admin page of the NAS?
no not at all
look at the LCD on the front of the N5200 and wait for the LAN IP to appear. Write down the number and set your IP address to lie within that range i.e. if the N5200 has LAN IP of 192.168.1.1 then set to 192.168.1.20 say. Set your default gateway to 192.168.1.1 and set your primary DNS server to the same as well.Quote:
Originally Posted by wintergreen
Any luck connecting to the admin page?
Well, I had a closer look on what my NAS did and what I did with it and in general, I find the things true that I mentioned above. One only difference in that explanation is that, when you have a build in switch within your NAS. But that is the same situation, as you would add a switch “in front” of that NAS. With other words, that switch obviously connects the LAN ports an the NAS with one Network card in the NAS and so, all members that want be connected need a suitable address in the right network. Giving the second NAS-network card an address that fits, doesn't mean that automatically the other card is set up to the same net.
I would believe, you also could connect the WAN to your existing router and went through the configuration and choose a good address for the LAN, the second card in your device. Than connect it back as you want and it should work.
I am going to show you, what I just did on mine:
root@127.0.0.1:/# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:FD:11:30:AA
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:127755443 errors:0 dropped:0 overruns:0 frame:0
TX packets:98402516 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2668536765 (2.4 GiB) TX bytes:2478984725 (2.3 GiB)
Base address:0xd400 Memory:e8100000-e8120000
eth1 Link encap:Ethernet HWaddr 00:14:FD:11:30:AB
inet addr:192.168.2.254 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Base address:0xd500 Memory:e8120000-e8140000
here you see two eth-cards with their configuration. Eth1 is the LAN, eth1 the WAN and it is, what I used up to now, connected in my network.
Now I'll change eth1:
root@127.0.0.1:/# ifconfig eth1 down
root@127.0.0.1:/# ifconfig eth1 192.168.0.101 netmask 255.255.255.0 up
root@127.0.0.1:/# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:FD:11:30:AA
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:129024204 errors:0 dropped:0 overruns:0 frame:0
TX packets:99023869 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4101104889 (3.8 GiB) TX bytes:2901692844 (2.7 GiB)
Base address:0xd400 Memory:e8100000-e8120000
eth1 Link encap:Ethernet HWaddr 00:14:FD:11:30:AB
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Base address:0xd500 Memory:e8120000-e8140000
it got an address in my range, that was free.
Now, I attach a LAN cable to that connector too and so I can use all services, NFS, ftp, http one either eth0 with 192.168.0.100 or eth1 with 192.168.0.101, so that means, both connect to the same internal structures.
That again means, you would only need one oft them (could have some benefits to use both).
The one you want, however, that has to be configured to be a member in your network.
With other words, in case your NAS is build in that way as mine, you would also not been able to see your other network partners “through” the NAS, so from LAN to WAN port, at least not without routing.