Re: All advice welcome!

From: Martyn Fewtrell (mfewtrell@networkclub.co.uk)
Date: 10/14/02 

From: "Martyn Fewtrell" <mfewtrell@networkclub.co.uk>
Date: Mon, 14 Oct 2002 18:22:21 +0100

Thanks for your advice, enabling basic authentication seems to have solved
the issue.

I am a little confused as to why my existing two workstations appear to work
using the integrated Windows method when they are on the same workgroup
running under the same circumstance. Incidentally the username/password
account set up is the same across both of the XP machines and they are both
within the same workgroup so in theory and as you had advised I had expected
the integrated windows option to work.

Either way thanks for the advice. 

--
Martyn Fewtrell
mfewtrell@networkclub.co.uk
http://www.networkclub.co.uk
"IT Community" <it-community.online@microsoft.com> wrote in message
news:jrof37rcCHA.1496@cpmsftngxa09...
> You wrote:
> | I'm running a small network of three workstations established as a
> | workgroup.  I have one Windows 2000 machine with IIS running, one
Windows
> XP
> | Pro machine with IIS5 running and the third machine (the problem)
running
> | Windows XP with IIS5.  Both XP machines have the .NET framework
installed.
> |
> | The intention was to use the third machine as a development server to
take
> | away some of the stress from my two workstations, ease backing up etc.
> |
> | Using either FrontPage 2000 or Visual Studio .NET I can log on to edit
web
> | sites on both the first two workstations from any of the others by
> supplying
> | the administrator password for that machine.  I can log on to edit a web
> | site on the new machine from FrontPage 2000 installed on that machine
but
> | when I try to log on to edit a web site on the new machine from one of
the
> | other workstations, the username/password is rejected (the administrator
> | username/password for the third machine).
>
> Response:
> 1. Since this is a workgroup environment, there is no centralized account
> database as it is in a domain. You need to add intended users on all
> machines. These machines also need to have the same workgroup name to be
> visible to one another.
> 2. The administrator account you are currently logging in on a local
> machine will not work when trying to publish/access to a remote server.
> Your options are either using the same password for the administrator
> account on all machine, this will make Integrated Windows which is one of
> the default IIS authentication methods work transparently. Or Enable BASIC
> authentication and disable Integrated Windows authentication method, which
> will cause an authentication prompt when accessing a remote machine.
>
> Hope this clarify some for you.
>
> Please do not send email directly to this alias. This is an online account
> name for newsgroup participation only.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> You assume all risk for your use.
>
> Windows XP SP1
>
http://www.microsoft.com/windowsxp/pro/downloads/servicepacks/sp1/default.as
> p
>
> Windows 2000 SP3
> http://microsoft.com/windows2000/downloads/servicepacks/sp3/default.asp
>
> Resources to secure IIS:
> Q282060 Resources for Securing Internet Information Services
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q282060
>
> Microsoft IIS Bookstore: http://go.microsoft.com/fwlink/?LinkID=8279
>
> TechNet Security Best Practices:
>
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/
> bestprac/default.asp
>
>

Relevant Pages

  • Authentication Issues with Vista Clients
    ... I'm having an authentication issue with one specific user...we run SBS 2003 ... he's having issues with Sharepoint. ... and logged in with his account, I've noticed it's doing it on them, too. ... account on all three Vista workstations and not the XP workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: All advice welcome!
    ... security settings all started working as normal. ... enabling basic authentication seems to have solved ... > using the integrated Windows method when they are on the same workgroup ... > account set up is the same across both of the XP machines and they are ...
    (microsoft.public.inetserver.iis.security)
  • Re: HTTP 401.2 - No permissions: login failed because of server configuration
    ... Authentication path. ... You might as well not enable Integrated Windows ... I can solve the problem by settings both Anonymous and Integrated Windows ...
    (microsoft.public.inetserver.iis.security)
  • Re: Under what credentials does a web-page run?
    ... >> anonymous connection to use a domain account, ... >> However, when I turn off anonymous access, and use Integrated Windows, ... > If I set the authentication method to basic, ... the password is not actually sent to IIS. ...
    (microsoft.public.inetserver.iis)
  • Re: HTTP 401.2 - No permissions: login failed because of server configuration
    ... I can solve the problem by settings both Anonymous and Integrated Windows ... Authentication, ...
    (microsoft.public.inetserver.iis.security)