IIS 6 : Frontpage Server Extension (FPSE) problem

Hello,
I have a big issue with a web server for a month now, and I can't find any
solution.

I have a Windows 2003 Server Standard Edition with IIS 6 on it (I'll call it
"the server").
On this server there are 2 web sites :
First web site : www.domain.ext and an alias.domain.ext application running
..NET 1.1
Second web site : alias2.domain.ext application running .NET 1.1
On the first web site, there is a virtual folder, running .NET 2.0
Both web sites and the virtual folder runs FPSE.

Everything was ok for 2 years : I was able to connect the two web sites
running .NET 1.1 with Visual Studio 2003, and the virtual folder running
..NET 2.0 with Visual Studio 2005 using the public server name.

But one month ago everything broke down "for no reason" (I wasn't at office,
and nor the network administrator nor the system administrator can tell me
what they could do that could explain this problem).

The server is running on a DMZ 10.x.x.x, while my developement PC is running
on a local network 192.168.x.x. I was also able to connect the web server
from outside with my laptop, using the public domain names. The network
administrator opened everything on the firewall between the DMZ and the
local network in order to be sure there isn't any problem caused by the
firewall.

As it didn't work anymore, and I wasn't even able to login the FPSE
administration pages, I decided to reinstall IIS, with not any success, then
:
- I took a unused Windows XP Professional PC (I'll call it "the backup
server"), installed IIS 5.1 on it, then installed the first web site on it
(the most important) with FPSE.
- Set every network parameters exactely the same as the server.
- Unplugged the server network cable, and plugged the backup server instead.
=> As a result, the backup server is just replacing the server

The web site is available with this configuration, and I can connect it
using Visual Studio 2003 from the local network as expected.

So I completely reinstalled Windows on the server, installed IIS 6 with the
2 web site and the virtual folder, installed FPSE, and installed it on the
local network (192.168.x.x).
I can connect to every sites using VS 2003 and VS 2005 (according the .NET
version installed of the different instances) when the server in on the
local network.

So, I tried to set the server network parameters for the DMZ, then unplugged
the backup server and plugged the server instead.

As expected, the web sites runs fine.

BUT... FPSE doesn't work anymore, I can't connect on it with VS 2003 or VS
2005. I have most of the time this message :
"Folder http://www.domain.ext isn't available. Server is busy or
inexistant."
Several times, I don't have a message, but get a message "Can't connect
using Frontpage Extension, try to select another method :" and not any
listed works (file share). Sometimes, it asks me for the server password
then... opens "My documents" folder (on my dev computer !)

I just can't understand what is the problem. I spent the whole afternoon
with the network admin, trying to find out is there was a DNS, ARP table or
other thing that could cause this, but we can't find anything.

More information about the network settings :
- DNS Server : 192.168.0.199 > References all the three public names of the
server as 10.1.1.11 (IP of the server in the DMZ)
- Local network router : 192.168.0.160 > Directly connect to the ISP
- Firewall : local network address : 192.168.0.197 / dmz address 10.1.1.254
/ not any blocking rules between the two sub networks
- DMZ router : directly connected to the firewall with a crossed cable. The
firewall references it as a third network.

The server network configuration (and the backup server when it was in use)
:
Not in domain
host : web
ip : 10.1.1.11
mask :255.0.0.0
router : 10.1.1.254
dns : ISP dns (194.2.0.20 / 194.2.0.50)
nothing else
not any anti-virus or firewall installed, microsoft windows firewall
disabled

My dev computer (Windows Vista running VS 2005) :
Not in domain
host : portsd
ip : 192.168.0.10
mask : 255.255.255.0
router : 192.168.0.160
dns : 192.168.0.199
nothing else (no firewall or anti-virus)
host file : only loopback address

My dev computer bis (Windows XP Pro running VS 2003 in a Virtual PC 2007 on
my Vista computer) :
Not in domain
host : virtsd
ip : 192.168.0.11
mask : 255.255.255.0
router : 192.168.0.160
dns : 192.168.0.199
nothing else (no firewall or anti-virus)
host file : only loopback address

On my dev computer, we also tried to use the router 192.168.0.197 in order
to directly point to the firewall, but without any change : it always works
when trying to connect the backup server using VS 2003, but fail to connect
the server using VS 2003 or VS 2005.

IIS on the server :
Site 1 : host : www.domain.ext / alias.domain.ext / any network interface
Site 2 : host : aias2.domain.ext / any network interface

IIS on the backup server :
Site 1 : host : www.domain.ext / alias.domain.ext / any network interface
(and not site 2 nor virtual folder using .NET 2.0 as the IIS 5.1 on XP Pro
doesn't allow more than one web application)

Well. Currently I'm quite disapointed. Please help...

Regards,
Sylvain

Re: IIS 6 : Frontpage Server Extension (FPSE) problem

Hello,

I still didn't find any problem. I really need some help.
Could someone tell me where to find a technical documentation of FPSE ?

"Sylvain" a écrit dans le message de
news:eH4lwbv9HHA.2140@TK2MSFTNGP06.phx.gbl...
> Hello,
> I have a big issue with a web server for a month now, and I can't find any
> solution.
>
> I have a Windows 2003 Server Standard Edition with IIS 6 on it (I'll call
> it "the server").
> On this server there are 2 web sites :
> First web site : www.domain.ext and an alias.domain.ext application
> running .NET 1.1
> Second web site : alias2.domain.ext application running .NET 1.1
> On the first web site, there is a virtual folder, running .NET 2.0
> Both web sites and the virtual folder runs FPSE.
>
> Everything was ok for 2 years : I was able to connect the two web sites
> running .NET 1.1 with Visual Studio 2003, and the virtual folder running
> .NET 2.0 with Visual Studio 2005 using the public server name.
>
> But one month ago everything broke down "for no reason" (I wasn't at
> office, and nor the network administrator nor the system administrator can
> tell me what they could do that could explain this problem).
>
> The server is running on a DMZ 10.x.x.x, while my developement PC is
> running on a local network 192.168.x.x. I was also able to connect the web
> server from outside with my laptop, using the public domain names. The
> network administrator opened everything on the firewall between the DMZ
> and the local network in order to be sure there isn't any problem caused
> by the firewall.
>
> As it didn't work anymore, and I wasn't even able to login the FPSE
> administration pages, I decided to reinstall IIS, with not any success,
> then :
> - I took a unused Windows XP Professional PC (I'll call it "the backup
> server"), installed IIS 5.1 on it, then installed the first web site on it
> (the most important) with FPSE.
> - Set every network parameters exactely the same as the server.
> - Unplugged the server network cable, and plugged the backup server
> instead.
> => As a result, the backup server is just replacing the server
>
> The web site is available with this configuration, and I can connect it
> using Visual Studio 2003 from the local network as expected.
>
> So I completely reinstalled Windows on the server, installed IIS 6 with
> the 2 web site and the virtual folder, installed FPSE, and installed it on
> the local network (192.168.x.x).
> I can connect to every sites using VS 2003 and VS 2005 (according the .NET
> version installed of the different instances) when the server in on the
> local network.
>
> So, I tried to set the server network parameters for the DMZ, then
> unplugged the backup server and plugged the server instead.
>
> As expected, the web sites runs fine.
>
> BUT... FPSE doesn't work anymore, I can't connect on it with VS 2003 or VS
> 2005. I have most of the time this message :
> "Folder http://www.domain.ext isn't available. Server is busy or
> inexistant."
> Several times, I don't have a message, but get a message "Can't connect
> using Frontpage Extension, try to select another method :" and not any
> listed works (file share). Sometimes, it asks me for the server password
> then... opens "My documents" folder (on my dev computer !)
>
> I just can't understand what is the problem. I spent the whole afternoon
> with the network admin, trying to find out is there was a DNS, ARP table
> or other thing that could cause this, but we can't find anything.
>
> More information about the network settings :
> - DNS Server : 192.168.0.199 > References all the three public names of
> the server as 10.1.1.11 (IP of the server in the DMZ)
> - Local network router : 192.168.0.160 > Directly connect to the ISP
> - Firewall : local network address : 192.168.0.197 / dmz address
> 10.1.1.254 / not any blocking rules between the two sub networks
> - DMZ router : directly connected to the firewall with a crossed cable.
> The firewall references it as a third network.
>
> The server network configuration (and the backup server when it was in
> use) :
> Not in domain
> host : web
> ip : 10.1.1.11
> mask :255.0.0.0
> router : 10.1.1.254
> dns : ISP dns (194.2.0.20 / 194.2.0.50)
> nothing else
> not any anti-virus or firewall installed, microsoft windows firewall
> disabled
>
> My dev computer (Windows Vista running VS 2005) :
> Not in domain
> host : portsd
> ip : 192.168.0.10
> mask : 255.255.255.0
> router : 192.168.0.160
> dns : 192.168.0.199
> nothing else (no firewall or anti-virus)
> host file : only loopback address
>
> My dev computer bis (Windows XP Pro running VS 2003 in a Virtual PC 2007
> on my Vista computer) :
> Not in domain
> host : virtsd
> ip : 192.168.0.11
> mask : 255.255.255.0
> router : 192.168.0.160
> dns : 192.168.0.199
> nothing else (no firewall or anti-virus)
> host file : only loopback address
>
> On my dev computer, we also tried to use the router 192.168.0.197 in order
> to directly point to the firewall, but without any change : it always
> works when trying to connect the backup server using VS 2003, but fail to
> connect the server using VS 2003 or VS 2005.
>
> IIS on the server :
> Site 1 : host : www.domain.ext / alias.domain.ext / any network interface
> Site 2 : host : aias2.domain.ext / any network interface
>
> IIS on the backup server :
> Site 1 : host : www.domain.ext / alias.domain.ext / any network interface
> (and not site 2 nor virtual folder using .NET 2.0 as the IIS 5.1 on XP Pro
> doesn't allow more than one web application)
>
> Well. Currently I'm quite disapointed. Please help...
>
> Regards,
> Sylvain
>