No login on https://my.ip/admin on 4.2.21

[nasmk]

Hi all,

I am Dutch and try to ask my first question here.

I have updated my Readynas Ultra and I can't get in the admin page.
Today I upgraded to 4.2.21 and I can't get in my admin page.
When I login the SABnzbd there is no problem.
And it still running.
I have tried to ad the second lag kabel en let hem get a new IP and try to het the admin page but it doesn't work.



:? why can't I login the admin page ? and why can I login SABnzbd?

can some one help me?

greats from holland......

[HERBIEO]

Try doing OS Re-install http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu
OS Re-install. Reinstalls the firmware from the internal flash to the disks. Use the OS reinstall boot mode when the system crashes and corrupts some configuration files.OS reinstall boot mode also resets some settings on your unit, such as Internet protocol settings and the administrator password, to defaults.

[nasmk]

HERBIEO...


Done..... but now nothing is working even SABnzbd......
There is a new ip but it doesn't let me login......

PS: I have no backup

[HERBIEO]

Dont worry OS reinstall does not destroy your data, try clearing your browser cache,
what ip are you using ???

[HERBIEO]

You did not do a factory reset did you ???

[nasmk]

No Did no factory reset ... can I do that without losing data?

and with ip 192.168.x.xxx

Tried another browser and empty the cache no results.

But its so strange RAIDar can find the NAS with status green..... and no problems STRANGE

hope you can help me

[HERBIEO]

No do not do factory reset >WARNING! The factory default reboot process resets the unit to factory settings, erases all data, resets all defaults, and reformats the disk to X-RAID2.
what password are you using to log in with ?

[StephenB]

The OS reinstall resets the admin password to the default netgear1. (As Herbieo says, it does not destroy data).

[nasmk]

When I use the admin and password it's possible to login with AFP (netgear1)
But the admin doesn't let me login it says:

Safari cannot get the connection and the same with chrome (using a mac)

[StephenB]

Maybe it is a security exception because the IP address changed. Try firefox, it is a bit simpler to click-through the warnings.

[HERBIEO]

Can you see any of the shares and access them from computer ?

[nasmk]

StephenB : downloading and trying it
HERBIEO: yes with AFP and CIFS

[HERBIEO]

Well there can not be much wrong if raidar reports eveything ok and you can access shares ok,
probably a small issue somewhere like StephenB says.

[nasmk]

Firefox can not connect to the server at 192.168.2.102.

Beats me.........
the same problem with other PC's no admin login and not with iPhone and iPad

[HERBIEO]

Try rebooting your router and then reboot the nas

[nasmk]

Strange will try that let you all know.... thanks for trying to help

[nasmk]

Done..... no results same there
AFP OK
CIFS OK
RAIDar OK
Safari, chrome and firefox cannot connect to the server

[nasmk]

Done..... no results same there
AFP OK
CIFS OK
RAIDar OK
Safari, chrome and firefox cannot connect to the server

[nasmk]

Done..... no results same there
AFP OK
CIFS OK
RAIDar OK
Safari, chrome and firefox cannot connect to the server

[HERBIEO]

Strange maybe you need to open a support ticket. https://my.netgear.com/myNETGEAR/support.asp

[nasmk]

done..... will wait an post the report when i got it done....

When there are any suggestions let me know

[StephenB]

nasmk wrote:
Firefox can not connect to the server at 192.168.2.102. Beats me......... the same problem with other PC's no admin login and not with iPhone and iPad

192.168.2.102 is a bit unusual address range. The PC address is also 192.168.2.x?

Can you ping the IP address?

[nasmk]

StephenB:

I live in germany my router is .1 and my DHCP is 100 - 200
I had a .10 but after the reset its now again in the DHCP range
When I login in the router my nas is connected and its possible to ping it.

Must be a software problem it worked for 2 moths on 4.2.20.....
After the reinstall it has a problem

[StephenB]

So you typed the IP address wrong in your earlier post? It is in fact 192.168.1.102?

[nasmk]

my bad

192.168.2.1 router
dhcp 192.168.2.100 - 200

srry haha