File/Program Association oddity

[DaveLembke]

Trying to figure out how to resolve this issue with a Windows 7 system. The other system that is connected to the NAS is Windows XP and doesnt have this issue.

On the Windows 7 system, when opening up a FileMaker Pro ( .fp5 ) file, it wants you to chose the default program all the time before opening. Yet it has a checkbox option displayed that is greyed out that would allow for this option to be set in stone to associate the file with the correct program, yet it doesnt allow for you to check the checkbox to make it a permanent default.

I went into the Default Programs listing and checked there to see if there was an option there to set this as permanent and no success there.

I also thought that maybe its because the user account is a user account instead of admin, and so I elevated the privileges to admin for this account and logged in as admin. As admin it also is greyed out and not able to set as permanent.

Anyone have any suggestions on how this could be resolved?

For now the work around is that each time a FileMaker project is opened the users have to select the FileMaker program to open the file with vs it opening automatically without prompting. On the Windows XP Home system in the office here it doesnt prompt and it opens when told to do so. 

Images attached show the checkbox that is greyed no matter what is selected ( which i placed a red border around to point it out ), and the Default programs listing that shows the FileMaker Pro association to .fp5 files in which the system seems to want to double check with the user vs just opening the file.

*** NOTE: Looking back at the screenshot and reading it completely, i just realized that this might be Firefox asking and not Windows 7 asking what program to open this with. So maybe its a Firefox issue, although it smells like a Windows 7 issue because this box looks more like Windows 7 prompting vs Firefox.

Additional Info:   The users interact with a web page located on the NAS. From this web page there is a interface which has pointers to the files associated with the option selected. The user points and clicks on the interface for an option displayed and it calls for the system to go out and request this file from the NAS to open. The Windows XP system just simply opens the file, but the Windows 7 system I cant seem to find a way to set this as default and not prompt. So its either a Firefox or Windows 7 issue. No special settings were made to Firefox on both computers and both are running the latest version of Firefox which even though its Firefox complaining it seems to point the finger back at Windows 7 maybe. 

[attachment deleted by admin to conserve space]

[Salmon Trout]

Have a look at this, might help, as those dialogs are Firefox, not Windows, I'm pretty sure.

'do this automatically for files like this from now on' box greyed out'

https://support.mozilla.org/en-US/questions/971694

[DaveLembke]

Thanks for your help with this... but tried those 2 add-on's shared in the url you provided and neither of them fixed the issue.

The strangest part about this is that the Windows XP Home SP3 system running Firefox 34.0.5 has no problems and the Filemaker Pro document opens right up without prompting, and on the Windows 7 Home Premium SP1 system it has this issue and the browser is the same exact version. Both also are default config with nothing special added other than the change to the home page from the default.

If it was an issue with the NAS causing a "Content-Disposition: attachment header" issue with Firefox, then the Windows XP Home SP3 system should have the same problem as the Windows 7 system, but it doesnt so this is an odd issue that seems to point the finger back at the Windows 7 box needing some sort of tweak. 

[BC_Programmer]

https://addons.mozilla.org/firefox/addon/live-http-headers/

You can see what the http headers are here. Note that a server can send different data based on the client headers sent to it.

[DaveLembke]

Tried that addon and shared the info captured... I dont see any header info being captured from the NAS to the Workstations, but decided to post the captured content here in case something stands out that I am not picking up on. I also thought that maybe showing exactly how I am interfacing with the NAS might point something out as well, and since the sensitive data is on the NAS, the interface and page source has no confidential info and can be shared.

Here is the capture from the XP system:

http://clients1.google.com/ocsp

POST /ocsp HTTP/1.1
Host: clients1.google.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 Firefox/34.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Length: 75
Content-Type: application/ocsp-request
Connection: keep-alive
0I0G0E0C0A0   +
HTTP/1.1 200 OK
Content-Type: application/ocsp-response
Date: Fri, 12 Dec 2014 13:12:44 GMT
Expires: Tue, 16 Dec 2014 13:12:44 GMT
Cache-Control: public, max-age=345600
Server: ocsp_responder
Content-Length: 463
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Alternate-Protocol: 80:quic,p=0.02
----------------------------------------------------------
https://safebrowsing.google.com/safebrowsing/downloads?client=navclient-auto-ffox&appver=34.0.5&pver=2.2&key=AIzaSyD-s-mXL4mBzF7KMRkhTCIbG2RKnRGXzJc

POST /safebrowsing/downloads?client=navclient-auto-ffox&appver=34.0.5&pver=2.2&key=AIzaSyD-s-mXL4mBzF7KMRkhTCIbG2RKnRGXzJc HTTP/1.1
Host: safebrowsing.google.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 Firefox/34.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Length: 223
Content-Type: text/plain
Cookie: PREF=ID=19b3b64fdb78686a:TM=1409939602:LM=1409939602:S=SpO-a3fWqOGmRTGp
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
goog-badbinurl-shavar;a:27844-37403:s:31762-40762
goog-downloadwhite-digest256;a:5-50:s:2-32
goog-malware-shavar;a:151397-160658:s:143308-151424
goog-phish-shavar;a:356925-363874:s:190214-192822,192824-193833,193835-195761

HTTP/1.1 200 OK
Alternate-Protocol: 443:quic,p=0.02
Content-Length: 104
Content-Type: application/vnd.google.safebrowsing-update
Date: Fri, 12 Dec 2014 13:12:44 GMT
Server: HTTP server (unknown)
x-content-type-options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Firefox-Spdy: 3.1
----------------------------------------------------------

Here is the capture from the Windows 7 system:

https://safebrowsing.google.com/safebrowsing/downloads?client=navclient-auto-ffox&appver=34.0.5&pver=2.2&key=AIzaSyD-s-mXL4mBzF7KMRkhTCIbG2RKnRGXzJc

POST /safebrowsing/downloads?client=navclient-auto-ffox&appver=34.0.5&pver=2.2&key=AIzaSyD-s-mXL4mBzF7KMRkhTCIbG2RKnRGXzJc HTTP/1.1
Host: safebrowsing.google.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Length: 209
Content-Type: text/plain
Cookie: PREF=ID=4985703c77ebd6c9:TM=1418390090:LM=1418390090:S=JHkMmZcqs2pm8k93
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
goog-badbinurl-shavar;a:27844-37404:s:31762-40763
goog-downloadwhite-digest256;a:5-50:s:2-32
goog-malware-shavar;a:151397-160659:s:143308-151425
goog-phish-shavar;a:356925-363875:s:190214-192822,192824-195762

HTTP/1.1 200 OK
alternate-protocol: 443:quic,p=0.02
Content-Length: 104
Content-Type: application/vnd.google.safebrowsing-update
Date: Fri, 12 Dec 2014 13:22:12 GMT
Server: HTTP server (unknown)
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
X-Firefox-Spdy: 3.1
----------------------------------------------------------

Here is the page source for the user interface:

Code: [Select]

<HTML>
<TITLE> Grievance Assistant Web Interface 1.0 </TITLE>
<BODY>
<center><img src="layout2014.bmp" usemap="#layout2014" style="border-style:none">
<HR>
<center><h5> Interface Created 4/25/2014 - Dave Lembke</h5>
<HR>

<div>
<map id="layout2014" name="layout2014">
<area shape="rect" alt="2011 Grievances" coords="586,139,689,222" href="2011G.lnk" title="2011 Grievances" />
<area shape="rect" alt="2012 Grievances" coords="695,139,800,222" href="2012G.lnk" title="2012 Grievances" />
<area shape="rect" alt="2013 Grievances" coords="587,225,688,308" href="2013G.lnk" title="2013 Grievances" />
<area shape="rect" alt="2014 Grievances" coords="696,225,801,307" href="2014G.lnk" title="2014 Grievances" />
<area shape="rect" alt="2010 Grievances" coords="772,557,855,640" href="2010G.lnk" title="2010 Grievances" />
<area shape="rect" alt="2009 Grievances" coords="678,559,760,641" href="2009G.lnk" title="2009 Grievances" />
<area shape="rect" alt="2008 Grievances" coords="581,557,664,641" href="2008G.lnk" title="2008 Grievances" />
<area shape="rect" alt="2007 Grievances" coords="490,557,572,640" href="2007G.lnk" title="2007 Grievances" />
<area shape="rect" alt="2006 Grievances" coords="396,557,478,639" href="2006G.lnk" title="2006 Grievances" />
<area shape="rect" alt="2005 Grievances" coords="304,558,386,639" href="2005G.lnk" title="2005 Grievances" />
<area shape="rect" alt="2004 Grievances" coords="210,556,293,639" href="2004G.lnk" title="2004 Grievances" />
<area shape="rect" alt="2003 Grievances" coords="118,557,200,639" href="2003G.lnk" title="2003 Grievances" />
<area shape="rect" alt="2002 Grievances" coords="25,557,108,641" href="2002G.lnk" title="2002 Grievances" />
<area shape="rect" alt="1723's" coords="450,449,533,550" href="1723.lnk" title="1723's" />
<area shape="rect" alt="3189's" coords="555,449,639,552" href="3189.lnk" title="3189's" />
<area shape="rect" alt="Assets" coords="661,449,745,551" href="asset.lnk" title="Assets" />
<area shape="rect" alt="2240's" coords="237,342,321,444" href="2240.lnk" title="2240's" />
<area shape="rect" alt="Bid Assignments" coords="555,341,639,444" href="Bid Assignments.lnk" title="Bid Assignments" />
<area shape="rect" alt="Editors" coords="130,449,216,551" href="editors.lnk" title="Editors" />
<area shape="rect" alt="FMLA" coords="343,448,427,552" href="FMLA Self & Family.lnk" title="FMLA" />
<area shape="rect" alt="Info" coords="769,342,854,444" href="info.lnk" title="Info" />
<area shape="rect" alt="Extensions" coords="660,342,746,444" href="extens~1.lnk" title="Extensions" />
<area shape="rect" alt="Maintenance" coords="449,342,534,445" href="maint.lnk" title="Maintenance" />
<area shape="rect" alt="Retirees" coords="770,448,854,551" href="retirees.lnk" title="Retirees" />
<area shape="rect" alt="Make-Ups" coords="131,342,215,445" href="make-ups.lnk" title="Make-Ups" />
<area shape="rect" alt="Vouchers" coords="237,449,322,551" href="voucher.lnk" title="Vouchers" />
<area shape="rect" alt="Non-Members" coords="24,342,109,445" href="Non-members.lnk" title="Non-Members" />
<area shape="rect" alt="Steward's Release Appeal" coords="342,342,427,445" href="Steward's Release Appeal.lnk" title="Steward's Release Appeal" />
<area shape="rect" alt="Members" coords="84,115,279,334" href="members.lnk" title="Members" />
<area shape="rect" alt="NLRB Charge" coords="316,113,573,335" href="NLRB Charge.lnk" title="NLRB Charge" />
<area shape="rect" alt="Address Labels" coords="24,449,110,551" href="Address Labels.lnk" title="Address Labels" />
<area shape="default" nohref="nohref" alt="" />
</map>
</div>
</BODY>
</HTML>
Here is the local path that the interface resides at with the .lnk shortcuts that point to the data location on the NAS at Z: drive as copy/pasted from browser window. ( Maybe because its not calling a HTTP or HTTPS this may be why its not being captured with that addon since its a local call to load page from, which then the targeted shortcut as referenced in hyperlink triggers to open the Filemaker Pro file associated with it at the NAS at Z: ):

file:///C:/New_GA_Interface/GrAssist1.htm

Attached Pics show the interface the user see's and interacts with point and click, as well as pic of the local directory tree and shortcut path info to the NAS at Z:

**Also, the reason for not using direct URL paths to the NAS at Z: and going with shortcut.lnk's is because when coded up with direct paths to Z:, then both systems wanted to download the file from the NAS, and this hyperlink path to shortcut was a trick to trick the system into thinking that the content was local, in which the shortcut to the NAS would trigger the file to open with no problems on the Windows XP system, BUT the Windows 7 system while the shortcut method avoids a download instruction from the NAS, prompts for File/Program association, even though the association is already defined in the shortcut in the "open with" under General Tab of the shortcut properties. As seen in last pic here.

It would have been a big problem if users were downloading individual copies of files and the data not written back to the NAS, so this was the method to avoid that. 


[attachment deleted by admin to conserve space]