RE: DCOM was unable to communicate with the computer 10.x.x.x

Tech-Archive recommends: Fix windows errors by optimizing your registry

I did also notice I only get this barrage of errors each day between 10am-10pm

"Jim Reed" wrote:

> yes the client.
>
> "Donald Francis" wrote:
>
> > Would this be on the client or the server? I assume you mean the client
> > since what you talking about only seems to show in the XP flavor of DCOMCNFG.
> >
> > "Jim Reed" wrote:
> >
> > > OK i was asking because i ran into and issue with XP sp2 and had to configure
> > > the dcom to allow anonymous connections. Here are the directions i had to do.
> > >
> > > 1. From the Start menu, click Run and type Dcomcnfg.exe.
> > > 2. In Component Services, click Console root, click Component Services,
> > > click Computers, and then click My Computer. On the Action menu, click
> > > Properties.
> > > 3. In the My Computer Properties dialog box, on the COM Security tab, in the
> > > Access Permissions section, click Edit Limits.
> > > 4. In the Access Permissions dialog box, grant Anonymous Logon allow Remote
> > > Access.
> > > 5. Restart the computer.
> > >
> > >
> > > I hope this helps some.
> > >
> > >
> > > "Donald Francis" wrote:
> > >
> > > > The vast majoriy are XP SP2 with just a few Xp SP1 and Win2k SP4..
> > > >
> > > > "Jim Reed" wrote:
> > > >
> > > > > What os on your clients?
> > > > >
> > > > >
> > > > > "Donald Francis" wrote:
> > > > >
> > > > > > BAH! Sorry..
> > > > > >
> > > > > > This is SMS 2003 SP1, the OS its running on is Server 2000 SP4
> > > > > >
> > > > > > "Jim Reed" wrote:
> > > > > >
> > > > > > > What OS and service pack?
> > > > > > >
> > > > > > > "Donald Francis" wrote:
> > > > > > >
> > > > > > > > DCOM was unable to communicate with the computer 10.x.x.x.x using any of the
> > > > > > > > configured protocols
> > > > > > > >
> > > > > > > > When looking at "system" in the even viewer I have this error message for
> > > > > > > > many many clients over and over again on my SMS 2003 SP1 server.
> > > > > > > >
> > > > > > > > SMS APPEARS to be working ok. I have looked all over and could not find
> > > > > > > > anything relavent to this situation for SMS.
> > > > > > > >
> > > > > > > > Anyone have any ideas?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Donnie
.

Relevant Pages

  • RE: id- 1030 source - Userenv
    ... Thanks for using the SBS newsgroup! ... I understand that the issue to be: all client ... computers got 1030 error and can not connect to the SBS 2003 server box. ... Click Internet Protocol, ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Web Workplace - Connect to client workstations
    ... In Connect to Client desktops item lists all client computers on your SBS ... network that are running Windows XP or above; In Connect to Server desktops ... On the Tools menu, click Internet Options. ...
    (microsoft.public.windows.server.sbs)
  • RE: Domain naming issue
    ... computers discover other computers on the network. ... so that the client computers resolve .local names correctly. ... you can configure a Macintosh computer ... One thing that will support desktop sharing with a Mac is Microsoft Office ...
    (microsoft.public.windows.server.sbs)
  • Re: Users cant find SBS server- Help needed
    ... all appears to be working except that no computers show up ... under the domin name in windows network and the client computers don't see ... the server in their windows network. ... The server still does not show up in Network places nor does any other ...
    (microsoft.public.windows.server.sbs)
  • RE: Unable to connect to Server/Client desktop using RWW
    ... When you remotely connect to Server Desktops (Client Desktops) ... Please verify all computers have allowed users log ... We can download the Remote Desktop Web Connection from Microsoft web ...
    (microsoft.public.windows.server.sbs)