I'm using Windows 7 Ultimate x64 and Expression Web 2, both with all
updates/service packs installed. This Win 7 rig is a 100% fresh build of
hardware and software, not an upgrade.
Problem: I cannot connect to my remote FP Server Extension based sites with
EW2. HOWEVER, I have no problems connecting with my ASP.Net sites and
publishing changes.
On my previous system, Vista Ultimate x64 and EW2, there were no problems at
all. I could make changes to the sites locally, then connect to the FPSE
remote sites and publish. But with this new Win 7 rig, I cannot figure out
what is causing the problem, though I've tried everything I can think of over
the past 48 hours, even uninstalling/reinstalling Expression Studio 2,
various reconfigs of the built-in IIS server, IE8, etc.
Details:
1) After installing all of the applications, I copied all of my websites
from the Vista rig to an external drive, then copied them over to the Win 7
hard drive. Basically, everything seems to be back in their rightful
locations.
2) With EW2, I can open my local FPSE sites, make changes, etc.
3) When I try to publish (or connect to) an FPSE site, I go through the
routine of selecting FPSE Site for the remote site, enter the http url, click
OK. Then EW2/Win 7 throw me a "Windows Security" username/password box. I
enter the information, then click OK...and the same box reappears asking for
the username/password again. No matter what I do, it doesn't seem to take the
info I give it.
4) I can't connect to the FPSE sites to open them, import them, publish to
them, etc., whatsoever.
I've confirmed it's not a problem with the FPSE extensions on the hosts,
because I've tried this on FPSE sites with both GoDaddy and NetSol. No luck
on either host.
If I switch back to my retired Vista rig...no problems at all, which
confirms it's something local to the new Win 7 rig trying to connect to the
FPSE sites.
I'm a long time user, since the FP98 days, so I've gone through all the
scenarios I can think of to get a connection. I have a feeling there's a
wrong setting somewhere in the IIS configuration (built into Win 7) or
perhaps IE8's settings. But at this point, I'm lost and don't know what else
to try.
More details: The Win 7 rig is a fresh build, not an upgraded machine. All
software was re-installed from the product DVDs, not a Win Easy Transfer,
then configured. I went through the same routine 3 years ago when I built the
Vista x64 rig and installed EW2 then. In Control Panel > Turn Windows
Features On/Off, I've matched settings as best I can from the Vista rig to
the Win 7 rig.
ODD NOTE: On the first build of this Win 7 rig, I did do a Win Easy Transfer
from Vista. Everything came across ok and this problem did not occur. I was
able to connect to all my FPSE sites without issue. But I didn't like the way
the Easy Transfer brought along some Vista remnants (pollution), so I wiped
the Win 7 drives and reinstalled Win 7, EW2, etc., again from the DVDs. And
now I have the problem. This is another clue that leads me to believe there's
a setting not right on the Win 7 rig.
This is killing me...and it's Turkey Day. I'm beat up, hungry, tired. I
don't want to have turkey dinner till I get this fixed...you know how it is.
I'm going to keep trying things while I check here for any responses.
Any help would be greatly appreciated.
I'll scan the other forums you suggest, but they're more likely to punt me
back here if they don't know the answer either.
--
Cheryl D Wise
http://by-expression.com
"James2008" <Jame...@discussions.microsoft.com> wrote in message
news:752CD873-9F62-43DB...@microsoft.com...
Not really, it's an IIS/Win 7 issue. No one would rationally suggest this
is an EW issue.