| reply to CampMaster
Re: Zywall fw 4.01 out For remote http access you need to provide a rule in your FW security.
You need 'Wan to Wan/Zywall' and permit access on any address (Source & Destination) for service HTTP(TCP:80).
Further you can only perform management from one place. So if you r already loged in localy then you can't do it from remote site at the same time and vise versa.
In the 4.00 firmware series you get a warning that admin is already loged in ... your screenie looks like equivalent warning.
Erwin |
|
 stefaanEPremium
join:2002-07-10
Luxembourg
kudos:1
 ·rapidxen
1 edit | reply to CampMaster
I get that message when restarting my browser when it crashes while a session with the ZyWALL is active. I had a look at the source code of the status screen and this message is generated by a Javascript function:
function doLoad()
{
if(location.href.substring(0,4)=="file")
{
logout2();
return;
}
if((document.referrer=="")||(document.referrer.substring(7,10)=="www")||(document.referrer.substring(7,13)=="search"))
{
alert("Warning:The device configuration is logging out now...");
logout();
}
}
Then the code tests for the strings "www" and "search" after the "http://" part of the referrer URL. In your case, this is "http://www.xxxxxx.com:1188" so when the ZyWALL refreshes the Status screen (which sets the referrer to the above URL) it will log off. The code seems to be present in all the screens generated by the ZyWALL, and hence you'll be forcibly logged off whatever page you access.
You could try and use another name for the address (one that doesn't start with www or search) and if my analysis is correct you should be able to administrate your ZyWALL.
I haven't read the manual so it could be a feature :) .
Take care,
Stefaan
--
"Technically, Windows is an 'operating system,' which means that it supplies your computer with the basic commands that it needs to suddenly, with no warning whatsoever, stop operating." -Dave Barry
|
|
 CampMasterRather Be Camp'nPremium
join:2001-05-16
Trabuco Canyon, CA | Your analysis was right on the money, a different name resolved the issue!
I am sure it worked prior to the 4.01 upgrade, but I could be wrong?
THANKS!
~CMT
--
There's no place like 127.0.0.1 |
|
stefaanEPremium
join:2002-07-10
Luxembourg
kudos:1 Reviews:
·rapidxen
| said by CampMaster:Your analysis was right on the money, a different name resolved the issue! I am sure it worked prior to the 4.01 upgrade, but I could be wrong? THANKS! Thanks a lot for the feedback. I'm quite sure this bit of Javascript code is not in the 4.00 release. I never used the remote management facility, but I'm sure you're right when you say it worked in previous releases of the firmware.
I think it's some kind of bug in a feature that was probably introduced to stop active "Status" screen connections from being hijacked by restarting the browser, thus circumventing the login process.
Take care,
Stefaan
--
"Technically, Windows is an 'operating system,' which means that it supplies your computer with the basic commands that it needs to suddenly, with no warning whatsoever, stop operating." -Dave Barry |
|
| Guess what?
FW 4.01(XD.0) is back on the Zyxel site. The .pdf doc is now 2 pages shorter. The .bin still the same.
I don't get it ...
Erwin |
|
| reply to sniper__e
said by sniper__e:So you reverted back to FW 4.00(xx.xx) and your last know good backup. If the RIP suggestion from Stefaan does not help you then something else is going on here. Are you sure your ADSL modem gets its synchronisation over the line? To test, unplug the power from this modem for 3 minutes and see what happens when you start it up again ... If artifacts are possible on a Zywall (? never seen that before) then perhaps try to load this new 4.00(WZ.11)C0 for your Z35. If nothing else is working then you can't lose anything by trying this one ... PS Why 3 min? Then i also know that your account information is dropped at the ISP's central. Let us know the results, Erwin I have disabled RIP on the WAN interface, but don't work. Then I try to change to another ADSL modem and use WAN2 port, also can't work.
I also try to restore to v4.00(WZ.11) and default ROM, but the route changes "by itself" after 2 seconds.
Now I am using Z10W, it works perfect, so I can confirm the ADSL modem & line is OK, only the Z35 has problem. |
|
| Has anyone noticed a PING problem on 4.01 when tring to ping through a VPN from the ZyWALL command prompt.
We have 3 ZyWALL 35 that we upgraded to 4.01 that are all interconnected via a VPN mesh. I can no longer PING the internal IP of any of the other machines through the VPN from the ZyWALL command prompt. The VPN's however are up and functional. All that happens is the "Resolving....." prompt is displayed but no stats as though the packets have been lost or not responded to.
We have another system with a VPN between a ZyWALL 35 (running 4.01) and a ZyWALL 5 (running 4.00). Pinging from 4.00 to 4.01 and everything is fine, but not the other way.
Packets are certianly reaching and being responded to by the destination ZyWALL. Maybe this is in someway related to the Trace Route issues I read briefly about. |
|
|
|
3 edits | reply to idolclub
said by idolclub: Now I am using Z10W, it works perfect, so I can confirm the ADSL modem & line is OK, only the Z35 has problem. If u still can, RMA it. With the 4.00(xxx) it should work because it allways has been working before.
Maybe the artifacts that Stefaan was talking about are in the game here ... but i suggest u don't talk about that in your RMA request.
Take care,
Erwin |
|
