fvdw-sl-console for ms windows install without removing HDD

[NasaMan]

So I tried the following things:
- set the rights for cunc open, tftp server, nc
- Shutdown Windows Firewall complete
- Shutdown Router Firewall
Nothing works. Allways the same picture like in previous screenshot. What I regognize is that the drive flashes two tines red when I enter a wrong IP Adress at FVDW-SL console. Bit it doesn`t helps because of the wrong adress...

EDIT: Tried portforwarding UDP69 for the drive.. no way. I think I will try the disambling methode tomorrow

[fvdw]

very odd this problem

there is a second tftp server included in the package, you can not use it for installation of the firmware as it will transfer only file from server to the nas and max size of 32 MB. But we can use it to load the standalone kernel and see if the tftp server is the problem

you can start it by opening a cmd window in windows 7 and goin to the directory were you installed the fvdw-sl-console files

Type as command in the windows 7 cmd window when being in that directory

Code: Select all

tftpd.exe [full path to tftp folder]

replace [full path to tftp folder] by the actual path to the tftp folder without the brackets but with quotes in case the path contains spaces
The path must also include the drive letter
example
C:\fvdw-sl-console\tftp

Temporarily rename the file in fvdw-sl-console folder with name tftpd32.exe to tftpd32-org.exe
This to prevent that the console will start the tftp server (two server s running will not work)

Now start the fvdw-sl-console and choose action to load standalone kernel. It will try to start tftpd server but it won't succeed but the script will continue to wait for u-boot

ps don't forget to rename the tftpd32-or.exe file afterwards

ps2 I don't understand what you mean with "wrong ip address" Also with using 192.168.0.252 it should flash two times red. In principle any ip address accessible in the LAN should work only for telnet access you need to use the specified ip address

[NasaMan]

no way... I get the telnet error again. I recognized that I have to hold the power on button for 5 seconds. Then I get the two red flashes. Yesterday I hold it only for 2 seconds. But it doesn´t changes anything (with cmd way and the u-boot setenv ipadd ${ipaddr}.... way :(

EDIT: I opened manually UDP69 in router and windows firewall but also no changes. I will disassemble the drive and try it with the linux way. Thank you for your patience

[fvdw]

there must be something not set ptoperly in your network if it also cannot find the simple tftp server.

Funny thing is that you can communicate with u-boot but not transfer a file form the tftp server to the nas. The difference is that when using the u-boot console you go from inside your windows pc to the NAS. Typically windows 7 will allow that if you have granted clunc-open and nc access to the LAN

If the nas tries to get a file from the tftp server running on the windows PC it will search the net for a tftp server listing on the default port. Apperently your windows PC doesn't respond to such a request, as result it can not find the tftp server

[NasaMan]

Mhh and I tried with two different PC`s... That is very strange

[fvdw]

leaves the router as suspect

some routers run a tftp server like cisco..if that is the case or anther device is running a tft server or another service at the default tftp port then this might also be an explanation for the problem

[fvdw]

in windows 7 you can see which port i used by tftpd32.exe (the tftpd server used)
Task manager , tab performance button source control

tftpd32l.JPG

[NasaMan]

It looks like the port isn't 69 in my case... Can I change it? What could be the reason?

[fvdw]

you should look in "listeners ports"

I have a similar entry in tcp ports but to see if it is listening and accessible you should look in the "listener ports"

[NasaMan]

I gave it another try. I took my old router and disabled the complete windows firewall (win 7). I disabled also the wlan connection. But it was the same. The drive flashed red for 9-10 times. The tftpd32 window is empty (only path and server ip is filled, rest is white). :hammerhead