OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Edwin Schild (edwin.schildINAME.COM)
Date: Wed Dec 05 2001 - 06:31:38 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hi guys (and girls),

    I have been using CoInitializeSecurity on both sides to make sure the
    security matches. I have been trying to connect using IP address and
    name. I have used CISCNFG and still no luck. Each time when I have
    rebooted the Win98 machine, it takes 15 minutes to connect from my Win2k
    machine to the Win98 server. Any other suggestions

    Edwin

    -----Original Message-----
    From: Henk de Koning [mailto:henkkCOMPLEXIT.COM]
    Sent: Tuesday, December 04, 2001 19:42
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: CoCreateInstanceEx takes 15 minutes in Peer to peer

    Another potential cause for this is actually a security problem. The SCM
    will by default try to authenticate the RemoteActivation RPC call (which
    will be used by down level clients inside the implementation of
    CoCreateInstanceEx) on authn level connect. When the call fails, the
    client SCM retries for every protocol in the protseq list and only after
    that retry with authn level none. You can manually set the authn level
    for the activation call in your call to CoCreateIjnstanceEx by filling
    in the COSERVERINFO struct (the pAuthInfo member).

    -- Henkk
    .
    ----- Original Message -----
    From: "Edwin Schild" <edwin.schildINAME.COM>
    To: <DCOMDISCUSS.MICROSOFT.COM>
    Sent: Monday, December 03, 2001 12:19 AM
    Subject: CoCreateInstanceEx takes 15 minutes in Peer to peer

    I have connected a Win98 and Win2k machine in a peer to peer network. On
    the Win98 machine I have my DCOM server running. I have enabled DCOM and
    Remote Connect. On my Win2k machine I have a client program that tries
    to connect to the Win98 server. The client progrem call
    CoCreateInstanceEx and that call takes between 900 and 901 seconds so
    that's 15 minutes. This only happens the first time. After that it takes
    only 0.02 seconds. When we reboot both systems, the connection takes 15
    minutes again. Anyone knows what we can do about this? We have tried
    using fixed IP addresses, dynamic addresses as used by Win98 and Win2k
    but still no luck. When we install IE5 or IE6 on the Win98 machine and
    it reboots at the end of the installation, then it works fast but when
    we reboot again, it is slow again.

    Edwin

    -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    Edwin Schild
    Nicolet Technologies B.V.
    -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html . To unsubscribe,
    mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html . To unsubscribe,
    mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM