Problems with OWA login from W2K

From: Esa Moilanen (cygnum_at_gmx.net)
Date: 02/22/05 

Date: Tue, 22 Feb 2005 16:12:36 GMT

Hi there,

I have the following setup and problem:

A newly installed Windows SBS 2003 with a small client base consisting of
Windows 2000 Pro SP4 machines and Windows XP Pro SP2 machines. All machines
have been successfully included in our domain. All file services, Outlook
2003 client as well as our SharePoint intranet runs without problems on
every machine.

Unfortunately Outlook Web Access (within our Intranet) works without
problems only for the XP clients. The W2K clients all get the same login
error:

533 - User not allowed to log on at this computer; Login type: 8 (= Network
Cleartext); Advapi; Negotiate; Process 5144; Port 1153

Interestingly enough the SBS "administrator" can log on to OWA from the W2K
stations, but not a "user" who has administration rights on the server.

I will be most grateful for your advise.

Thanks in advance

Esa

Relevant Pages

  • Re: Firewall Client Deployment
    ... I am deploying ISA Server's Firewall Client 2006 to client machines ... Windows XP Professional SP2. ...
    (microsoft.public.isa.clients)
  • Re: Site and content rules
    ... support anonymous users on specific machines with assigned ... If you goal is to manage Internet access based on Windows ... not reference client sets, ... also references your Windows security group and your Users ...
    (microsoft.public.isa)
  • Re: How to add site boundaries programmatically?
    ... Windows 98 machines won't install the client unless the ... We've been using a virtual switched network here that makes it look ...
    (microsoft.public.sms.admin)
  • Re: [long rant] Call this a f**king OS...
    ... it is a bloody Windows rant. ... Both machines happily talk to the wireless router and access the ... network that has been happily functioning for 3 years now. ... I have no idea why and the client is ...
    (uk.comp.sys.mac)
  • Re: MS Outlook is "hijacking" email over OE!
    ... I'm surprised the problem isn't> more widespread...its happened on two of our machines> with different office and windows versions, and we aren't> doing anything too out of the ordinary! ... >>>>Make OE the default e-mail client: ... >>> We use Outlook Express for our email. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)