Sandeep,

Ok I can now access JWEB over the ge-0/0/0 interface. However this is an unacceptable solution and is a government security guideline violation. As you are already aware the loopback interface is the known best practice interface for network device management. Can we please open a feature request with the JUNOS engineering team?

For now we have no choice but to use ge-0/0/0 for management. Why management on lo0 was removed makes no sense at all. 

-DC


A Note has been logged to your Case #2011-0705-0549
Synopsis: configuration issue

Customer Tracking: 

You may view or edit case 2011-0705-0549 online at:
https://www.juniper.net/cm/case_email_link.jsp?case_number=2011-0705-0549

07/06/11 09:45:18 

This is the follow-up mail for case 2011-0705-0549. There is change in Junos behavior after 10.2 Junos version related to J-Web.
From 10.2R3 onwards if we configure a loopback interface lo0 for HTTPS or HTTP , this will ensure that the web-server will rejects 
all the J-Web access request.

So , you have to remove the lo0 interface from system services web-management hierarchy and use other external interfaces to access the J-Web.

You can find more information regarding this in the release notes for Junos 10.2 Version.
http://www.juniper.net/techpubs/en_US/junos10.2/information-products/topic-collections/release-notes/10.2/topic-45729.html#rn-junos-srx-j-CIDBS

Please find more information in above mentioned link under J-web section.

I also tried calling you to discuss with you on your phone number 757-541-5577 , but unfortunately reached your voice-mail.

Please try above mentioned changes and update me if you are still facing any issues.



Regards,
 
Sandeep Rana
JNCIA-JunOS JNCIS-SEC JNCIS-ER JNCIS-ENT