Focus on Microsoft
MS 2000 DUN Connection Name issue Feb 03 2004 03:29PM
Micheal Patterson (micheal tsgincorporated com) (1 replies)
Re: MS 2000 DUN Connection Name issue Feb 04 2004 11:01PM
Nate (njmorris softhome net)
We had this problem when the DCOM settings on a Windows 2000 or higher PC
were changed. In our case we did the following to create/resolve the problem:

1. Click Start, Run, then type dcomcnfg and press enter.
2. Click the Default Properties tab.
3a. To create the problem, change the Default Impersonation Level to
"Anonymous".
3b. To solve the problem, change the Default Impersonation Level "Identify".
4. Click OK then reboot.

Here is a KB article on this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;254631

Setting DCOM Impersonation to Anonymous also caused problems with Windows
Installer in some scenarios.

I hope this helps.

Nate

At 09:29 AM 2/3/2004, you wrote:
>This morning, one of my remote sites called in stating that all of their DUN
>connection icons had disappeared. We proceeded to re-create them and when
>prompted to name the connection, any character combination that was entered
>was declared invalid. Has anyone else seen this? I've googled and can only
>locate one other incident of this listed on Jan 27 2004. I'm suspecting that
>this may have something to do with a trojan/virus but I've not gotten enough
>information to make that determination.
>
>Thanks.
>
>--
>
>Micheal Patterson
>TSG Network Administration
>405-917-0600
>
>Confidentiality Notice: This e-mail message, including any attachments, is
>for the sole use of the intended recipient(s) and may contain confidential
>and privileged information. Any unauthorized review, use, disclosure or
>distribution is prohibited. If you are not the intended recipient, please
>contact the sender by reply e-mail and destroy all copies of the original
>message.
>
>
>
>-----------------------------------------------------------------------
----
>-----------------------------------------------------------------------
----

------------------------------------------------------------------------
---
------------------------------------------------------------------------
---

[ reply ]


 

Privacy Statement
Copyright 2010, SecurityFocus