Problems with IE7 and Explorer as FTP client

[Guest]

For years, I've been using XP Pro. I use Windows Explorer as my FTP client.
It's very easy to do. You just type in your FTP site in the address box, hit
return, and then a login box pops up asking for a user name and password.

I can do the same with Vista, but there's a real difference in the
functionality, and I'm having real trouble getting Vista Explorer (not IE,
but the file explorer) to behave in the same way XP's Windows Explorer does
when used as an FTP client.

In XP Pro, if I log in to my FTP site, and want to view a particular html
file (for example, to view it before deleting it), I don't need to transfer
the file to my local drive. I just click on the html file and because Windows
Explorer knows that all html files are to be viewed using IE, the file opens
in its own IE popup window. I can then view the file, and make a decision
about whether I want to delete it or leave it on the server (I should note
that the FTP server is running a message board, which gets literally
thousands of hits a day, and given the volume of traffic on the site, it's
much easier to simply view the files and either leave them or delete them
without actually doing an FTP file transfer to my local drive).

In Vista, the same Explorer functionality is there, but here's the catch:
When I click on an html file, IE 7 opens up a window (actually it opens a new
tab...but I think I know how to change that by changing the settings in Tabs
to have "Popups Open in New Window"). But here's the real problem: When the
html file is opening, and before it will display, I'm presented with an FTP
login box, which requires me to again input my username and my password to my
FTP site.

This is a huge pain in the ass, and it literally takes away the
functionality of using Explorer (file explorer that is) as an FTP client. If
I have to log in every time I want to view an html file in IE just to view
the contents of my remote FTP directory, given that I am looking at many
hundreds, if not thousands of individual files a day, it's just not practical
to keep re-entering my username and password before IE 7 will display each
file.

Anyone know why this is happening, and more importantly, how I can change
this behavior in Vista? I've searched all of the settings in IE 7 under Vista
and there doesn't appear to be any way to disable this constant log-in dialog
before being able to view an html file on my remote ftp server.

Any help would be greatly appreciated.

 

[DevilsPGD]

In message <[email protected]> Jerry

This is a huge pain in the ass, and it literally takes away the
functionality of using Explorer (file explorer that is) as an FTP client.

No, it doesn't. This lets you use Explorer as an FTP client just fine,
there just isn't any specific interaction between your FTP client and
webbrowser, just like any other webbrowser.

More importantly it's a case of process separation between Explorer and
IE, which is a good thing, although it unfortunately causes some loss of
convenience.

 

[Guest]

In message <[email protected]> Jerry


No, it doesn't. This lets you use Explorer as an FTP client just fine,
there just isn't any specific interaction between your FTP client and
webbrowser, just like any other webbrowser.

More importantly it's a case of process separation between Explorer and
IE, which is a good thing, although it unfortunately causes some loss of
convenience.

Gee, thanks for the help. I didn't ask for an editorial response about
whether separating processes was "better". Instead I asked if someone knew
how to restore what you call the "convenience" which from my perspective IS
"functionality."

Maybe someone else has a better idea about how to limit the security logins
in IE7? The real issue is why does IE7 in Vista (unlike IE7 in XP Pro) lose
persistence when it comes to a login to a website, and how can one make IE7
work the same way in both OS's?

 

[DevilsPGD]

In message <[email protected]> Jerry

Gee, thanks for the help. I didn't ask for an editorial response about
whether separating processes was "better".

Welcome to usenet.

Instead I asked if someone knew
how to restore what you call the "convenience" which from my perspective IS
"functionality."

True -- There are a lot of things which are inconvenient, but required
for security. This is one example.

Maybe someone else has a better idea about how to limit the security logins
in IE7? The real issue is why does IE7 in Vista (unlike IE7 in XP Pro) lose
persistence when it comes to a login to a website, and how can one make IE7
work the same way in both OS's?

Use IE7 as an FTP client directly -- Explorer and IE are two entirely
different FTP clients which don't (and thanks to process separation,
cannot) interact.

 

[Guest]

And your response is why I will never purchase another Microsoft product
again. Keeping processes "separate"? Are you nuts. IE7 is capable of
reading html. If you're logged in, then you should stay logged in. If IE7
is the registered reader for html, then activating an html file in Explorer,
by double clicking on it, should not require yet another layer of "security".

But again, thanks for all of your concern.

______________________________________
If you want a kind word, try putting down the 2x4