Re: SSO fails when machine is connected to network

I have downloaded Microsoft's DCOMTEST.EXE program and verified that DCOM
functions from/to this machine via its machine name, pegasus. All the
resources I can find indicate that the RPC server not being available is a
symptom of DCOM failure - must be something else. Anyone have any ideas?

"Bill Sayles" wrote:

> Sorry, I wasn't very clear. The problem was when I tried to configure a
> receive port. I added an entry to both the hosts and lmhosts files and I
> tried it again. It failed with the following message inthe event log:
>
> SSO AUDIT
> Function: GetConfigInfo
> Tracking ID: dec584ae-f9c3-4afa-83cc-8cb38eb08c37
> Client Computer: pegasus (BTSNTSvc.exe:3304)
> Client User: PEGASUS\BTSUser
> Application Name: {7D0BB3CB-299D-41DC-BC25-FA7DBE6EF546}
> Error Code: 0x800706BA, The RPC server is unavailable.
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> (this message came when I tried to delete the receive port to add it again)
>
> I tried this earlier (but hosts only, since lmhosts is deprecated) based on
> a KB article about error 0x80070005 return code 2. That time the
> ConfigFramework failed on SSO config saying that a 127.0.0.1 entry was
> invalid.
>
> I have a named workgroup using the name of the machine. I tried resetting
> the group back to WORKGROUP, but it acted like I was on a workgroup called
> WORKGROUP rather than having none assigned. Perhaps I should change the name
> of the machine and maybe some errant setting will be reset.
>
> Or maybe I can assign another IP to a different adapter ( my firewire
> network adapter or add another explicit loopback) that is not 127.0.0.1.
>
> I have taken can of ForceGuest and Lsa/RPC registry settings.
>
> "Jon Flanders[MVP]" wrote:
>
> > It has to do with the way components connect to SSO - they do this through
> > DCOM. What usually is the case is that your machine name changes when you
> > hook up to the network.
> >
> > The easiest way i've found to fix this problem is that add a line in the
> > hosts file that maps the machine name to 127.0.0.1 - but YMMV
> >
> > --
> > Jon Flanders
> > http://www.masteringbiztalk.com/blogs/jon/
> >
> > "Bill Sayles" <Bill Sayles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:C31C1E02-6C97-4BF8-8B76-9E130171B1E2@xxxxxxxxxxxxxxxx
> > >I was trying to configure my installation of BizTalk 2004 (w/0 sp1, client
> > > does not have it) and I kept getting the following error or a variant.
> > >
> > > [12:59:26 AM Info ConfigFramework] Showing MessageBox with text: Failed to
> > > enable the Single Sign-On (SSO) Service (error code 0X800706BA). Return
> > > Code: 4
> > >
> > > I searched and found a variety of possible solutions, including registry
> > > changes, and performed them to no avail. I only succeeded at
> > > ConfigFramework
> > > when there was no active network, wireless or wired.
> > >
> > > When I tried to deploy a simple solution, it failed. When I disabled my
> > > wireless adapter thereby effectively mimicking the case when the
> > > configuration completed, the solution deployed.
> > >
> > > I could not test it because I needed the network for some of the ports,
> > > but
> > > in any event this will not work for the long term.
> > >
> > > Does anyone have any idea why removing the network seems to bypass the
> > > errors? What can I do to correct the situation?
> > >
> > > Thanks.
> > >
> > > Bill
> >
> >
> >
.

Relevant Pages

  • Re: Network Neighborhood
    ... > inability to browse by using Network Neighborhood in Windows 95 or Windows ... > communicated effectively with the other workgroup computers. ... > not have a common networking protocol, a common workgroup, and common user ... the computer that is running Windows ...
    (microsoft.public.win2000.networking)
  • Re: WindowsXP and RISC OS computers
    ... >> - You can however ping Nixiyo from the windows XP machine, ... > workgroup: WORKGROUP ... > Name as M$ calls it, had been changed on the centrex machine. ... > Neither icon appears in My Network Places on the centrex. ...
    (comp.sys.acorn.networking)
  • clarification sought in using XP Pro laptop for domain at work and workgroup at home
    ... I am inquiring for a friend. ... The XP Pro laptop was once configured for a two-computer workgroup. ... "WORKGROUP" as the name of its network affiliation. ...
    (microsoft.public.windowsxp.network_web)
  • Re: help understanding authentication on workgroups
    ... network client services on and print/file sharing on), ... workgroup authentication is said to be ... the password for that guest account on that computer, I get access to that PC ... The browser provides visibility. ...
    (microsoft.public.windowsxp.network_web)
  • Re: help understanding authentication on workgroups
    ... network client services on and print/file sharing on), ... workgroup authentication is said to be ... the password for that guest account on that computer, I get access to that PC ... The browser provides visibility. ...
    (microsoft.public.windowsxp.network_web)