Rick, just reinstalling IIS is a quick and painless process, so I would try that before nuking your system. If you like I can do a remote desktop session with you and have a quick look.
On Sat, Apr 30, 2011 at 7:02 PM, Rick Faircloth <[email protected]>wrote: > > Nothing's working... not changing permissions, not > deleting and re-creating the default web site... nothing. > > At this point, I'm ready to flush the entire system and > reinstall from scratch. I can have that done in a day > and be back to work. > > Any last ditch suggestions before I nuke this system? > > > -----Original Message----- > From: Rick Faircloth [mailto:[email protected]] > Sent: Saturday, April 30, 2011 1:42 PM > To: cf-talk > Subject: RE: Can't open cfadmin after installing CFBuilder Beta 2 > > > Many thanks, Jenny, for the help last night! > > So, far, however, nothing has solved the problem. > I removed all 172... IP's, but that didn't help get > localhost working. I worked some more with permissions, > since some of the error messages related to that, but couldn't > come up with any access permissions that solved the locahost > issue, either. > > At this point, I'm going to follow Russ Michael's suggestion > and delete the default web site and create a new one and see > if the current one is corrupt. > > If you read this, Russ, any caveat's for this process of > deleting the default web site? (Totally inexperience with this > action...haven't ever had to do this....) > > > > -----Original Message----- > From: Jenny Gavin-Wear [mailto:[email protected]] > Sent: Saturday, April 30, 2011 11:44 AM > To: cf-talk > Subject: RE: Can't open cfadmin after installing CFBuilder Beta 2 > > > Rick and I worked through this problem last night. > > We got rid of the IPV6 and that got the localhost pinging correctly, then > we > encountered problems with IIS 7. If you have IPV6 installed a ping to > local > host will reply with :::1 instead of the usual 127.0.0.1 address. > > Rick had been advised to use a 172. series IP address to his config, even > though his LAN is on 192.168.x. He'd also been told to add lines to the > host file for each web site he works on pointing to the 172 IP. > > Rick is in the process of getting rid of the 172. IP and reconfiguring > IIS7. > Hopefully that will fix the problem. > > If you ever need to set up a line in the hosts file to point to a site in > development on your own PC, all you will ever need to point at is the > 127.0.0.1 local (loopback) IP. Naturally, you'll be the only one able to > access the site. If you want more people to be able to access the site > either set up a new dns record for it within your domain pointing to the > fully qualified IP address, or if you just want people on your LAN to see > it, point it to your servers local IP address. > > There are three IP address ranges reserved for LANs. Class A 10.x.x.x, > Class B 172.16.x.x and Class C 192.168.1.x. The only difference in these > classes is the maximum number of IP's they each make available. Typically, > for example, Class A is only used by large corporates using a large VPN. > > Jenny > No virus found in this outgoing message. > Checked by AVG - www.avg.com > Version: 9.0.894 / Virus Database: 271.1.1/3605 - Release Date: 04/29/11 > 18:08:00 > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:344095 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
