Frontpage server extensions?

[Sven]

Is there a way to enable Frontpage server extensions on the IIS7 beta hosting? As it stands I cannot connect to the server using Visual Studio 2008.

FTP access from within Visual Studio also fails with "501 Server cannot accept argument".

Any help?

EDIT: FTP connects now. It looks like it wasn't using passive mode despite me telling it to. Restarting VS fixed it. It's terribly slow though. And I'm getting various errors wrt opening and saving files.

EDIT2: And I can't upgrade the solution to ASP.NET 3.5. Keeps giving errors.

Post Edited (Sven) : 10/16/2007 11:17:07 AM GMT

[wisemx]

Sven, I don't know the details but there is a known problem with passive mode and some routers.
I've contacted Linksys and they confirm but don't have a solution other than not using passive mode.

Thought this might be worth mentioning...

[raymondp]

I'm afraid that Microsoft is trying to phase out FrontPage Server Extensions. It does not come on IIS7 and cannot be installed on it. Sorry.

rcp
DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)

[Aristotle]

Actually, Microsoft is currently working onan update for FrontPage extensions 2002that works in Windows Server 2008. AlthoughI wouldn't install it on a site because of its inherent problems with messing with permissions.

Aristotle

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)

[Sven]

I have no problems with phasing out FPSE as long as I get a suitable replacement. I love the ability to connect VS directly to my site instead of having to edit locally and then upload.

Connecting tothe IIS7 beta serverwith FTP from within Visual Studio 2008 isn't working at all. I get timeouts and other assorted errors (I have no idea if this is a problem with VS2008, IIS7 or your configuration).

If I can't get FPSE, fine, but at least give me a good alternative (this is more directed at MS than at DASP).

Is DASP planning on having FPSE on IIS7 (which as Aristotle indicated, is being worked on) once it goes gold, at least as an option? Or will FTP access be working right by then?

wisemx: I don't have a router. I'm running VS2008 withina virtual machine (VPC2007)with NAT networking with the host (so I have to use passive mode). The host PC is Vista x64 and connected directly to the Internet with a VDSL connection.

EDIT: Since connecting with FTP from VS2005 with active mode seems to work fine, it's either a issue with VS2008 or passive mode. Since I'll likely be able to use active mode when VS2008 comes out (when I'll install it on my machine for real and not in a VM), it might end up not being an issue.

Post Edited (Sven) : 10/26/2007 5:38:53 AM GMT

[wisemx]

Try posting that problem in the VS 2008 forum section at www.asp.net (http://www.asp.net)
The Msft reps there are pretty good about answering quickly.

MSDN also has a forum for VS 2008:
http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=153&SiteID=1

[Sven]

Ok, I've done some checking, and this is definitely Visual Studio's fault. Passive mode just isn't working right. Here's a capture of what's happening when I try to open web.config:
[quote]

34 1.340294 192.168.131.67 209.67.188.10 FTP Request: PASV
35 1.340628 209.67.188.10 192.168.131.67 TCP ftp > 1078 [ACK] Seq=352 Ack=105 Win=4090 Len=0
36 1.455208 209.67.188.10 192.168.131.67 FTP Response: 227 Entering Passive Mode (209,67,188,10,211,233).
37 1.455466 192.168.131.67 209.67.188.10 TCP 1080 > 54249 [SYN] Seq=0 Len=0 MSS=1460
38 1.590221 209.67.188.10 192.168.131.67 TCP 54249 > 1080 [SYN, ACK] Seq=0 Ack=1 Win=4096 Len=0 MSS=536
39 1.590288 192.168.131.67 209.67.188.10 TCP 1080 > 54249 [ACK] Seq=1 Ack=1 Win=65535 Len=0
40 1.590454 192.168.131.67 209.67.188.10 FTP Request: SIZE Web.config
41 1.590781 209.67.188.10 192.168.131.67 TCP ftp > 1078 [ACK] Seq=404 Ack=122 Win=4079 Len=0
42 1.734797 209.67.188.10 192.168.131.67 FTP Response: 213 1679
43 1.735034 192.168.131.67 209.67.188.10 FTP Request: RETR Web.config
44 1.736240 209.67.188.10 192.168.131.67 TCP ftp > 1078 [ACK] Seq=414 Ack=139 Win=4079 Len=0
45 1.861410 209.67.188.10 192.168.131.67 FTP Response: 125 Data connection already open; Transfer starting.
46 1.867194 209.67.188.10 192.168.131.67 FTP-DATA FTP Data: 1460 bytes
47 1.867223 209.67.188.10 192.168.131.67 FTP-DATA FTP Data: 219 bytes
48 1.867274 192.168.131.67 209.67.188.10 TCP 1080 > 54249 [ACK] Seq=1 Ack=1680 Win=65535 Len=0
49 2.000460 209.67.188.10 192.168.131.67 FTP Response: 226 Transfer complete.
50 2.000521 192.168.131.67 209.67.188.10 TCP 1078 > ftp [ACK] Seq=139 Ack=492 Win=65044 Len=0
51 2.188477 209.67.188.10 192.168.131.67 TCP 54249 > 1080 [FIN, ACK] Seq=1680 Ack=1 Win=4096 Len=0
52 2.188542 192.168.131.67 209.67.188.10 TCP 1080 > 54249 [ACK] Seq=1 Ack=1681 Win=65535 Len=0
53 2.188659 192.168.131.67 209.67.188.10 TCP 1080 > 54249 [FIN, ACK] Seq=1 Ack=1681 Win=65535 Len=0
54 2.190252 209.67.188.10 192.168.131.67 TCP 54249 > 1080 [ACK] Seq=1681 Ack=2 Win=4096 Len=0
55 2.205508 192.168.131.67 209.67.188.10 FTP Request: TYPE A
56 2.205806 209.67.188.10 192.168.131.67 TCP ftp > 1078 [ACK] Seq=492 Ack=147 Win=4088 Len=0
57 2.314240 209.67.188.10 192.168.131.67 FTP Response: 200 Type set to A.
58 2.314589 192.168.131.67 209.67.188.10 FTP Request: PASV
59 2.314915 209.67.188.10 192.168.131.67 TCP ftp > 1078 [ACK] Seq=512 Ack=153 Win=4090 Len=0
60 2.433502 209.67.188.10 192.168.131.67 FTP Response: 227 Entering Passive Mode (209,67,188,10,211,234).
61 2.433707 192.168.131.67 209.67.188.10 TCP 1081 > 54249 [SYN] Seq=0 Len=0 MSS=1460
62 2.616129 192.168.131.67 209.67.188.10 TCP 1078 > ftp [ACK] Seq=153 Ack=564 Win=65535 Len=0
63 5.420174 192.168.131.67 209.67.188.10 TCP 1081 > 54249 [SYN] Seq=0 Len=0 MSS=1460
64 11.429182 192.168.131.67 209.67.188.10 TCP 1081 > 54249 [SYN] Seq=0 Len=0 MSS=1460
65 23.367565 192.168.131.67 209.67.188.10 TCP 1078 > ftp [FIN, ACK] Seq=153 Ack=564 Win=65535 Len=0
66 23.369001 209.67.188.10 192.168.131.67 TCP ftp > 1078 [ACK] Seq=564 Ack=154 Win=4096 Len=0
67 23.588284 209.67.188.10 192.168.131.67 TCP ftp > 1078 [FIN, ACK] Seq=564 Ack=154 Win=4096 Len=0
68 23.588360 192.168.131.67 209.67.188.10 TCP 1078 > ftp [ACK] Seq=154 Ack=565 Win=65535 Len=0
</CODE>
34 through 49 show how Visual Studio successfully(!) retrieves web.config. Then it switches to TYPE A, sends PASV again, andtriesto connect tothe wrong port. The response to PASV at number 60 indicates it wants the client to connect to port 54250, but instead Visual Studio is connecting again to port 54249, which was the correct port for the previous connection but not anymore. This fails of course, causing Visual Studio to proclaim it failed at retrieving the file (even though it had already successfully retrieved it earlier).

I'm going to bug this on connect. Hopefully they'll be able to get a fix into RTM. I'm not too hopeful though at this late stage.

[wisemx]

Thanks for making an updated note on this bro. http://community.discountasp.net/emoticons/wink.gif

[Sven]

Alright, I got a response from MS on my Connect issue on thispoint. Apparently it's related to IE6.

After updating the virtual machine to Internet Explorer 7 with all updates, Visual Studio 2008 can successfully connect to the IIS7 server using passive mode FTP.

So consider my request for FPSE hereby retracted. :)

[bruce]

this is interesting problem. I wonder if this is a bug. Why would IE cause problem with FTP!!!

Bruce

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)

[Sven]

I'm not sure. I guess VS2008 is using some component from IE to do the FTP requests and for some reason that goes wrong with IE6.