Closed Bug 266668 Opened 20 years ago Closed 19 years ago

Raritan Remote KVM Java client does not load

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: chrisehlers_uk, Assigned: bugzilla)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/0.9.3 StumbleUpon/1.995
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/0.9.3 

I enter the IP address of my raritan KVM box, it correctly redirects me to the
https://10.0.0.1/rrc.htm page, and then only displays the Raritan logo.  Where
with IE it displays the following 
» 10.29.2004 11:54:7.977 Raritan Remote Client loading...

» 10.29.2004 11:54:8.87 Raritan Remote Client launched.

» 10.29.2004 11:54:14.37 Raritan Remote Client closed.

» Press Refresh on your web browser toolbar to restart Raritan Remote Client.
And then opens the client to access the KVM.


Reproducible: Always
Steps to Reproduce:
1.Setup Raritan KVM with remote client version 4.00.69
2.Give it an IP address
3.Enable Java in the Options of firefox
4.Try and browse to the IP address of the raritan box.

Actual Results:  
Just loads the raritan logo and nothing else

Expected Results:  
Should open the raritan client.
Version: unspecified → 1.0 Branch
*** Bug 288675 has been marked as a duplicate of this bug. ***
Is it a Sun JRE issue, or Raritan writing to MS Java extensions? Set IE to use
Sun's Java (Internet Options, Advanced tab about halfway down) and see if you
duplicate the results.

In fact, what version of Java are you using with Firefox? If it's less than 1.5
I urge you to upgrade anyway for security reasons.

If so then decide if you want to complain to Sun, Raritan, or both. There may be
exceptions on the Java console which explain where the error is, and you could
look up on the internet to see if it's in an MS extension.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.