Locked-out of fvdw after long absence

[Fuddyduddy]

Dear fvdw

I'm sorry to have irritated you, as I so obviously have. You're quite wrong in your suspicion that I don't read the 'Help' pages before asking questions: I study them carefully, so obviously I must be a complete idiot. All the more need then for patient help, might I suggest?

In the midst as I was of trying to grapple with the idiosyncracies of not just one but two routers at one and the same time, it seemed self-evident that the words "You just need to enable the dynamic IP option in the LAN setup" referred to my router setup. "Dynamic IP" and "LAN" are networking terms are they not? It never crossed my mind that it was the fvdw web interface that was being referenced, so naturally I didn't look there for the answer on this occasion.

It would have been nice if you could have limited yourself to just correcting my misunderstanding, and spared me your disapproval. Wrestling with these technical problems isn't my idea of fun. Life's too short.

Nonetheless I'm forced to continue to ask for your help. I have now restored my LAN setup to the way it was at the outset: one router only (the newest). The immediate result is that I'm back where I started from so far as the fvdw NAS is concerned. I cannot find any way of getting it and my router to talk to each other. As a result I'm once again unable to access the fvdw Web interface and therefore can't carry-out any operations on the NAS via my desktop Windows PC.

My understanding (such as it is) is that a router is supposed to detect all network devices connected to it and automatically to assign them IP addresses within the range it uses. My router refuses to do that in relation to the fvdw NAS and - despite all Jocko's patient help - that's where I'm still stuck:- precisely where I came in.

If any more information is needed to help with diagnosis I'll do my best to provide it. I'm at a loss to know what else it is you think I should be contributing.

[Fuddyduddy]

About seeing shared folders, just type the ip address of your nas in explorer address bar

Code: Select all

\\ip-adres

(PS so do NOT use for this the web browser internet explorer but the explorer used to browse files on your pc !)

Yes I'm familiar with that process thanks, and aware of the difference between Windows File Explorer and a web browser.

Just one small problem though:- there's no communication whatever between my Windows PC and the fvdw NAS, with both of them connected to my Linksys router. fvdw's web interface therefore isn't accessible. Furthermore, the only IP address I have for the fvdw NAS is the one it was assigned by my previous router (now replaced), which does not accord with the range of IP addresses which the Linksys recognises. But it refuses to assign a changed IP address to the NAS which is within its own range.

Stalemate.

[fvdw]

Hi Fuddyduddy

oke explanation accepted and yes indeed I was irritated. I still find it strange when you ask were to set the automatic assignment of IP, as if you go indeed have gone through the web interface pages you should have find that page with lan setup and everything should be clear.

Now lets talk about your problem and try to solve it.
You mentioned that you had access to the webinterface of the nas using your buffalo router.
Then you can use the webinterface to change your nas from instead of having a static IP adress to getting an automatic assigned ip addres.
It is obvious that when you reboot, after making that change, that you need to have a dhcp server in your lan to get again access to the nas. It then doesn't matter anymore which pool of ip addresses is used by the dhcp server, it will assign one to the nas within its pool. So as well it should be able to access it when connecting it to your buffalo router and also your linksys router (assuming they have a dhcp server running)

;)

[Jocko]

Hi Fuddyfuddy

Can you explain what is it your lan configuration after setting the option "automatic assigned ip address".

For me it is no good to have two DHCP servers with two subnets because you can not known with what DHCP server the nas gets its IP lease

So I advice you to keep only your linksys router (main LAN) with its DHCP server running.

What windows OS do you have on your laptop ?

[Fuddyduddy]

@ Jocko

Can you explain what is it your lan configuration after setting the option "automatic assigned ip address"

Does this answer your question?

Note:- of all the devices shown the NAS is the only one not to have been assigned any IP address by the Linksys DHCP server.

[Fuddyduddy]

For me it is no good to have two DHCP servers with two subnets because you can not known with what DHCP server the nas gets its IP lease

So I advice you to keep only your linksys router (main LAN) with its DHCP server running

I couldn't agree with you more!

What windows OS do you have on your laptop ?

Windows 10 Pro

[Fuddyduddy]

You mentioned that you had access to the webinterface of the nas using your buffalo router.
Then you can use the webinterface to change your nas from instead of having a static IP adress to getting an automatic assigned ip addres.

Yes that's exactly what I thought. But when I had the NAS and my Desktop - and nothing else - connected to the Buffalo the Buffalo saw only my Desktop PC. So it's not only the Linksys DHCP server that won't play ball with the NAS but the Buffalo's too.

As a result I couldn't see any way in which to do what I was trying to do, which you also are suggesting, and thereby be able to progress to the intended final stage.

Clearly I must be missing some vital link in the chain.

(Note: In that temporary set-up, the Buffalo's Internet port was connected to one of the Linksys LAN ports. I also tried using a Buffalo LAN port but got no connection at all that way.)

[fvdw]

There is no need to connect your buffalo router to the linksys or to the internet to enable the dynamic ip setting on your nas.
Just set your buffalo router up with dhcp server enabled and set ip pool. (Of course as long as you didn't change the static ip address of your nas the ip pool should be 192.168.11.1 to 192.168.11.254.). If your pc is set to get an dynamic ip this could be done by just connecting your pc to your buffalo to a lan port and access the administration web server of the router. After that and if you made a change to the ip pool you need to reboot your buffalo router. Your pc stays connected and should be able to access the router after reboot. (Check it by accessing the admnin webserver of the router and check if ip pool isok). Now connect your nas to your buffalo router using a lan port, start it and access the nas, after it finished booting, on the static ip address you have set in the past via your browser on your pc. If this doesn't work then I can only think on wrong or defective utp cables used or a malfunction of your buffalo router

[Fuddyduddy]

Reporting back.

I once again connected only desktop PC and NAS to the Buffalo, switched back to 'router' mode. Then in fvdw Web interface -> System Management -> LAN ; activated "Automatically assign IP settings (DHCP)" radio-button. Next removed the Buffalo from the LAN and re-connected Linksys as sole router. Result:- Linksys assigned IP address to NAS in range 192.168.1.zzz.

Subsequently reserved the new NAS IP address in the Linksys web interface.

So the NAS is now back in business, on an identical footing with the other devices on my current LAN.

At present I still can't manage to access the fvdw system files in Windows: entering

Code: Select all

\\fvdwsl-base\

in Windows file explorer's address-line only produces a "can't find..." response at present. But I'm working on that.

[Jocko]

Hi Fuddyfuddy,

I once again connected only desktop PC and NAS to the Buffalo, switched back to 'router' mode. Then in fvdw Web interface -> System Management -> LAN ; activated "Automatically assign IP settings (DHCP)" radio-button. Next removed the Buffalo from the LAN and re-connected Linksys as sole router. Result:- Linksys assigned IP address to NAS in range 192.168.1.zzz.

Subsequently reserved the new NAS IP address in the Linksys web interface.

So the NAS is now back in business, on an identical footing with the other devices on my current LAN.

Ha it is what I asked now previously since several post! :pound

in Windows file explorer's address-line only produces a "can't find..." response at present. But I'm working on that.

Did you set the same workgroup on you nas and laptop ?
As you use windows10, maybe there is an issue with smb1. See fvdw's posthttps://plugout.net/viewtopic.php?f=27&t=2859#p27558