Huh? Which version of Firefox are you using? What is the webpage where that error message appears?

i am using mozilla firefox 25.0.1-2

i am using mozilla firefox 25.0.1-2. the webpage is http://www.ssconline.nic.in/tpform1.php?exam_code=MTN&year=2014&notice_no=F.No.3/11/2013-P%20and%20P-I&notice_date=16-11-2013

Yes, I'm seeing the same.

Did you try to continue anyway to see if it works with Firefox?

the same problem is occuring .

Does anyone knw hw to fixed this problem of netscape not supported in mozilla 26.

The website is incorrect if it identifies Firefox as Netscape and attempts to block Firefox as a result.

Firefox does have its' roots in Netscape, but Netscape has been effectively dead for almost 10 years now. Chances are that any website that sees "Gecko" and thinks that user has Netscape rather than Firefox is 'sniffing' the UserAgent string with old code that should have been retired years ago.

Websites may be using outdated browser detection software that doesn't work with the current Firefox release.

In case you can ignore this message and can continue then you can check if the site is working as it should when it supports modern browsers.
If the website only supports IE and uses proprietary MS (JScript) code that only works in IE then you are out of luck.

use the oldest version of the web explorer. it will surely work.

Solution for your problem is given clearly in the below website. http://online-computersolutions.blogspot.in Follow the steps in the website your problem will be solved

The solution linked by t.pradeep is for IE 11, not for Firefox.

The site uses this test to reject browsers other than IE and Opera:

if(navigator.appName=="Microsoft Internet Explorer" || navigator.appName=="Opera")
 {
  //alert("Valid");
  return;
 }else{
  alert(navigator.appName+" is not supported, Please use IE or Opera");
  return false;
 }

The User Agent Switcher extension modifies the appName property, so it should be able to fool this site. There was a bug in Firefox 25 that prevented that from working, but that bug was fixed in Firefox 26.