Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 1.0 and 1.1 > ASP.NET 1.0 and 1.1 Basics
Password Reminder
| FAQ | Members List | Search | Today's Posts | Mark Forums Read
ASP.NET 1.0 and 1.1 Basics ASP.NET discussion for users new to coding in ASP.NET 1.0 or 1.1. NOT for the older "classic" ASP 3 or the newer ASP.NET 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 1.0 and 1.1 Basics section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old November 28th, 2007, 02:02 PM
Registered User
Join Date: Nov 2007
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Visual Studio 2005 FrontPage Extensions Stumper

I'm currently helping a client solve a little FrontPage Extension stumper when editing their ASP.net project in a remote session via Visual Studio 2005.

The problem is that they're able to log in half the time, and half the they're not able to. When logging in to the remote development server via the I.P. address with VS 2005, they have no problems. The user credentials for the allowed accounts work just fine. However, when they try and log in to the remote development server using the URL which points to the same I.P. address, they are prompted with the authentication form, but no user credentials under any account work at all.

 I had initially thought that the URL isn't resolving to the I.P. address for some reason. I had tried and replicated the same problem under my own Virtual Dedicated hosting solution, but didn't have any problems with both the I.P. or URL scenario. I also fiddled on my own local host development machine, and did learn about the Configuring/Checking Server Extensions for respective web sites with the IIS manager. I've not had the chance to experiment with that on the development server that I'm discussing about with this problem. However, here are two details concerning the server in question:

A: The I.P. is behind a firewall, so there's no public access to the web site via the I.P. address, but the URL resolves just fine via a web browser for public access

B: The web server in question utilizes multiple I.P. address, as it hosts several different web sites from it. So, I'm beginning to wonder if the FPE are getting confused for some reason, not knowing which I.P. to point to, hence no authentication credentials will work?

 I even went so far as to snoop around the *.cnf files that are part of the FPE on a server to see if there was an tweaking, or manual changes that might be needed…but to no real avail as of yet.

So, any advice, web site, forum or blogs with any information and advice will be greatly appreciated!

Thank you



Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Can i use visual studio 2005 !! swapnil_sandy ASP.NET 2.0 Basics 2 November 2nd, 2006 12:40 AM
FTP in Visual Studio 2005 Pro (Visual Basic) shoopes VB How-To 1 June 29th, 2006 02:08 PM
Visual Studio 2003 vs. Visual Studio 2005 eitanbarazani C# 2005 4 May 9th, 2006 01:34 AM
Visual Studio .net2003 and Visual Studio 2005 Gert Visual C++ 1 January 24th, 2006 05:10 AM

All times are GMT -4. The time now is 04:36 PM.

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.