We normally access a web based application that contains links to launch specific sun java based secure .jnlp files.

 

All our PC's are part of a Windows 2003 domain environment. Group policy is active and controlling much of how the PC's operate.

 

Before we upgraded from IE6 to IE7, when a link to open one of these JNLP files is clicked, such as the link below (this is a secure environment so the link will not work from the outside. It is simply put here to better illustrate the problem), a dynamically created .jnlp file would launch and the sun java environment would load up and the java application the link points to would run.

 

"Locate" Link à https://www.mbnetstar.com/portal/site/NetStar4/menuitem.c1ec0ca12589df866630de310ca13453/NetStarDo%7CVISTA%7CLocate%7Ccom.mbusa.mbapps.trans.vistaNet.locate.LocateTransaction

 

"Inventory" Link  à https://www.mbnetstar.com/portal/site/NetStar4/menuitem.c1ec0ca12589df866630de310ca13453/NetStarDo%7CVISTA%7CInventory%7Ccom.mbusa.mbapps.trans.vistNet.inventory.InventoryTransaction

 

However, after upgrading to IE7, when this link is clicked (for example, the "Locate" link below) the...jnlp that is supposed to launch does not, and the internet explorer page shown below simply refreshes.

 

 

However, if I am on my laptop, which is not part of the domain, and I click on this same link, I get an internet explorer information bar message showing that the .jnlp file is trying to download.

 

 

At this point, I simply have to click the "download file" option as shown below to launch this...jnlp file.

 

 

Once I do this, on the laptop which is outside of the domain, the .jnlp file automatically opens up and begins to launch as shown below.

 

 

 

I then click "yes" to accept the security certificate as shown below.

 

 

 And shortly after doing this, the application opens up as shown below.

 

 

Given the fact that this worked without incident inside my domain when using internet explorer 6, and it works fine on a laptop that sits outside of the domain with IE7, what could possibly be causing this problem to occur on workstations that sit inside the windows 2003 domain? I changed nothing in any of the domain based group policy files I set up and this problem happens. I am certain the solution to this problem has to do with making some kind of group policy adjustment so this file/launch issue is handled exactly the way it is handled on my laptop, or handled on the same workstations when IE6 was there.

 

I am hoping that someone has some clue on this and could point me in the right direction. Initially, I thought it might be a mine type issue and make some changes in group policy, but that did not have any effect, so there has to be something I either missed, or I am not looking at this from the right standpoint.

 

I singlehandedly built our domain environment, and configured every group policy setting that is in effect so I am confident that I can get to the bottom of this with a slight "nudge" in the right direction, 

 

One interesting thing is that one link has always worked even after upgrading to IE7 and that is the link below

 

https://www.mbnetstar.com/portal/site/NetStar4/menuitem.31b1a6f4d9e3297fac4469740ca13453/?vgnextoid=51442812dc48e010VgnVCM10000048184335RCRD#

 

What is the difference between the link to this .jnlp file that still works in the domain since upgrading to IE7

https://www.mbnetstar.com/portal/site/NetStar4/menuitem.31b1a6f4d9e3297fac4469740ca13453/?vgnextoid=51442812dc48e010VgnVCM10000048184335RCRD#

 

And the 15-20 links that do not (example shown below)

 

"Locate" Link à https://www.mbnetstar.com/portal/site/NetStar4/menuitem.c1ec0ca12589df866630de310ca13453/NetStarDo%7CVISTA%7CLocate%7Ccom.mbusa.mbapps.trans.vistaNet.locate.LocateTransaction

 

"Inventory" Link  à https://www.mbnetstar.com/portal/site/NetStar4/menuitem.c1ec0ca12589df866630de310ca13453/NetStarDo%7CVISTA%7CInventory%7Ccom.mbusa.mbapps.trans.vistNet.inventory.InventoryTransaction

 

Etc.

 

The provider of the web application basically has told us that they refuse to assist us on this and they have adamantly said there are no problems with how they coded the links.

 

Any help would be greatly appreciated.