Need help getting my Network drive back

[sheeny]

A few weeks ago my network router died. I bought a new one but the DHCP addresses are not the same. On my old router the net drive was 192.168.1.111 (fixed address) but the new router addresses are all based around 192.168.0.1.

How can I get my net drive back accessible on my network?

Thanks in advance.

Al.

[supernova1965]

Can you ping for the address of the old network storage and if that works you should be able to map it on your computer

[supernova1965]

http://forum.qnap.com/viewtopic.php?p=270481

I think this is your solution

[alistairsam]

Hi Al,
Connect your laptop to the new router, open the router's page in your web browser, in this case http://192.168.0.1
enter the name and password, usually admin and password, but can vary
then go to the lan settings, there you should have a dhcp section.
it would show 192.168.0.
change the third octet to 1
thats 192.168.1.
save, it should reboot.
if you want to go back to the router settings, you'll have to then type in the new IP in your browser http://192.168.1.1 and you'll have access.
else you're done, and you should be able to get access to the 192.168.1.x devices. check the ip address for your laptop, it should have a 192.168.1.x address, if it does, you should be able to ping your nas at 192.168.1.111

[sheeny]

No go...:sadeyes:


Read promisingly but no go either.


Yep. This worked. I changed the IP to 192.168.1 and I'm away. I've also changed the setting in the NAS drive to automatic IP rather than fixed, so if it ever happens again it should adjust to suit automatically instead of having to manually change the network to suit the drive. I was a little wary of messing with this after the 3 days of headaches it took on the phone with support trying to get my new router going!:rolleyes:

Al.

[alistairsam]

Hi,
I'd suggest leaving it as static as the automatic IP can vary once the dhcp lease expires.
So you'll have more issues connecting to it as you'll need to know what the new IP is. the third octet won't change, just the fourth.
eg, it could have 192.168.1.84 today, after 6 days, it could have 192.168.1.86.
a very handy network scanner I use in my work is the softperfect network scanner. It has loads of options and helps identify what IP your devices have got in a range.
the download is in the lower half of the page
http://www.softperfect.com/products/networkscanner/

[mithrandir]

Any DHCP server worth the name (ie forget M$) follows the RFCs and will not change the IP allocated to a device. This is a MUST requirement. As long as you leave both the router and NAS on the IP will never expire.

If you don't care to trust DHCP, the router can probably be told to always assign a static IP for the NAS's MAC address.

As for network scanning, nmap does anything doable.

[alistairsam]

and what would happen if the NAS is inadvertently reset, the router reset, etc or there is a need to reset down the track?
if a device is to be permanently on the network and accessed by IP, either use static or use a DHCP reservation which is the second option mentioned.
In the router, set aside a block of 30 or 40 IP's for static devices, eg, in the dhcp scope settings, don't start the scope from the default, start it from say 30 or 50. so .2 to .29 or .2 to .49 are free to be statically assigned.

[acropolite]

I'm with Andrew on reservations in the DHCP table, that's the best method at least in my case, I have lots of devices connected and if they're statically assigned DHCP addresses then it's simply a matter of adding the MAC addresses to the router's static DHCP table. I use that method because I change routers fairly frequently, we do a lot of VOIP networking between PABX's and I often need to test routers for suitability before installation.

Another good trick is to set your PC as static adress with manual gateway and DNS setings and enter a number of alias IP's in the advanced TCPIP settings. That way it's possible to have for example, your LAN and router in the 192.168.1.x range, another device in the 10.0.0.x range, yet another in the 172.22.50.x range. We use that technique at work as the PABX's we install all come with different default IP addesses and often we need to access documentation on the LAN as well as download patches, licencing & sotware updates and program the PABX without changing it's IP address.

[alistairsam]

I guess its a question of personal preference and suitability as both dhcp reservations and static work well.
I use both on my LAN and WAN in different scenarios.
Once you decide on your subnet, eg. mine is non-default, you could assign required devices like NAS or servers with static, and if you get a new router, just adjust the scope to match your local subnet. Bit less fiddly than reservations. again, its upto ones preference.
For Al's application, both would work, if he can get the NAS's mac either via the routers arp table or current leases, he could add a reservation, else configure the nas. whichever's more convenient for him.