Re: RPC over HTTP is suddenly broken?

How have you configured this so that Outlook supplies the credentials? I
haven't been able to figure out how to do that.

GaryK

"Bryan L" <blinton.nospam@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eZ%23XrWIlFHA.2764@xxxxxxxxxxxxxxxxxxxxxxx
> Understandable. I emphasized to users they should have a password on
> their user account at home. They actually aren't getting email without
> credentials, strictly speaking; they just don't have to enter them as they
> are supplied automatically when they open Outlook. The entire session is
> encrypted over HTTPS so the wire is actually more secure than using basic
> authentication. Physical security to the home computer is the weakest
> factor here. They aren't concerned, and given the family life most of
> them have, it's pretty unlikely a malicious or stupid user would cause
> them problems.
>
> Some of our sales people use this on their laptops when they're out of the
> office, but unless they leave their laptop logged on and walk away from it
> (which they've been told not to do), a malicious user couldn't log into
> their user account or access email without knowing their cached domain
> credentials.
>
>
> "Gary Karasik" <gkarasik@xxxxxxx> wrote in message
> news:%23hNg7OIlFHA.320@xxxxxxxxxxxxxxxxxxxxxxx
>>> it configured to connect to our mailboxes without even prompting us for
>>> credentials.
>>
>> I'd be nervous allowing people to get email without credentials.
>>
>> GaryK
>>
>> "Bryan L" <blinton.nospam@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:%23qJYkyHlFHA.1968@xxxxxxxxxxxxxxxxxxxxxxx
>>> I've been using RPC over HTTP successfully for many months now. Half a
>>> dozen users, including myself, have Outlook 2003 installed at home and
>>> have it configured to connect to our mailboxes without even prompting us
>>> for credentials. It's wonderful. After applying all the components of
>>> SP1 for SBS 2003 several weeks ago, I tested RPC over HTTP and still had
>>> no problem with it.
>>>
>>> Cut to a few days ago.
>>>
>>> One of my users was having an authentication problem with his PocketPC
>>> when trying to synch with the server over its wireless connection via
>>> OMA . In attempting to fix the problem, I played with SSL and security
>>> settings for OMA in IIS, and finally re-ran the Configure Email and
>>> Internet Connection Wizard on the SBS, to no avail. In the end, his
>>> problem was finally solved by simply deleting and re-entering his
>>> password in his Pocket PC. (Geez.)
>>>
>>> Ever since then, RPC over HTTP has not worked. An Outlook 2003 client
>>> attempting to connect via HTTP is prompted for credentials. The title
>>> bar says "Connecting to sbsservername.domain.local". The "User name:"
>>> field is pre-populated with "DOMAIN\username", and the "Password:" field
>>> is blank. When a correct password is entered, it's rejected as though
>>> incorrect.
>>>
>>> The clients are correctly configured, but the server configuration has
>>> apparently changed.
>>>
>>> One other interesting note; Remote Web Workplace now has issues for
>>> users who do not already have the ActiveX control installed. A dialog
>>> box pops up saying: "This portion of the Remote Web Workplace requires
>>> the Microsoft Remote Desktop ActiveX Control. Your broswer's security
>>> settings may be preventing you from downloading ActiveX controls.
>>> Adjust these settings, and try to connect again."
>>>
>>> My initial thought on this was that the Internet Explorer security
>>> settings being configured via Group Policy had gone awry. I say this
>>> because in applying SBS SP1, the only step I forgot was to export my
>>> Group Policy configuration before applying the Service Pack components.
>>> Some settings were reverted to SBS defaults, and I've been changing them
>>> back as I notice them. The reason I don't think this is the real cause
>>> of the problem is this: it even happens to computers at home that
>>> aren't members of the domain. Lowering security settings to as low as
>>> possible does not correct this problem.
>>>
>>> Not sure how best to proceed at this point...any help appreciated.
>>>
>>> Thanks in advance,
>>>
>>> Bryan
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Terminal Services Security Issue with Cached Credentials
    ... should prevent users from logging onto the TS with cached credentials. ... You may also want to post in one of the Terminal Services ... configuration and user configuration. ... Services clients will be disabled and users will no longer be able ...
    (microsoft.public.windows.server.security)
  • Re: Outlook authentication over VPN
    ... You may just need to make 100% sure that these Outlook profiles have the Log ... On Network Security set to "None" in the Advanced Tab of the Microsoft ... currently logged on credentials, which in your case is the incorrect Local ... To configure Outlook 2000 to prompt you for your log on credentials, ...
    (microsoft.public.exchange2000.clients)
  • Re: RPC over HTTP is suddenly broken?
    ... credentials, strictly speaking; they just don't have to enter them as they ... In attempting to fix the problem, I played with SSL and security ... >> settings may be preventing you from downloading ActiveX controls. ... >> Group Policy configuration before applying the Service Pack components. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP is suddenly broken?
    ... I'd be nervous allowing people to get email without credentials. ... > have it configured to connect to our mailboxes without even prompting us ... > settings may be preventing you from downloading ActiveX controls. ... > Policy configuration before applying the Service Pack components. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to SQL Server on WIN2003 Box
    ... I only said that in a configuration that runs SQL and IIS (aspnet) on the ... it's impossible for us to tell whether the specified credentials are correct ... What's the point in having SQL ...
    (microsoft.public.dotnet.languages.csharp)
Loading