Creating remote objects on win95/workstations

[ranga raghunathan]

the CreateObject(progid,servername) function works only if the
servername specified is a windows nt server or a 2000 server but not a nt
workstation or a 2000 professional workstation ..this is not documented in
msdn library but there is a kb article on this - Q191121

does anyone know of any other function to create remote objects on win95/98
or workstations ?


thanks
ranga

[Mark]

I believe that client machine must have user-level authentication, ie) be
part of an nt domain, or connected to an nt workstation machine. This is
found in the last (?) tab of the network panel.

Then you must make sure that the class you want to invoke is allowed to be
invoked by remote users. This is configured using: dcomcnfg.

I hope that this is right - I haven't used Win98 in a while .

"ranga raghunathan" <ranga1@msn.com> wrote in message
news:3926a55c$1@news.devx.com...
>
> the CreateObject(progid,servername) function works only if the
> servername specified is a windows nt server or a 2000 server but not a nt
> workstation or a 2000 professional workstation ..this is not documented in
> msdn library but there is a kb article on this - Q191121
>
> does anyone know of any other function to create remote objects on
win95/98
> or workstations ?
>
>
> thanks
> ranga

[ranga raghunathan]

article 191121 says:
The documentation for the CreateObject function does not mention the server
referenced in the servername argument must be a Microsoft Windows NT Workstation
or Server.

For example, the following line of code should create and return a Microsoft
Excel application object from the specified server, if the server is a Microsoft
Windows NT Workstation or Server.

Sub Test()
Set xlObj = CreateObject("Excel.Application","\\MyServer")
xlObj.Visible = True
End

I suggest that before posting a question you should read the documentation
more than one time. It may sound a little bit rude
but try not to waste other people time.




"Mark" <please.dont@send.me.mail-use.the.newsgroup> wrote:
>I believe that client machine must have user-level authentication, ie) be
>part of an nt domain, or connected to an nt workstation machine. This is
>found in the last (?) tab of the network panel.
>
>Then you must make sure that the class you want to invoke is allowed to
be
>invoked by remote users. This is configured using: dcomcnfg.
>
>I hope that this is right - I haven't used Win98 in a while .
>
>"ranga raghunathan" <ranga1@msn.com> wrote in message
>news:3926a55c$1@news.devx.com...
>>
>> the CreateObject(progid,servername) function works only if the
>> servername specified is a windows nt server or a 2000 server but not a
nt
>> workstation or a 2000 professional workstation ..this is not documented
in
>> msdn library but there is a kb article on this - Q191121
>>
>> does anyone know of any other function to create remote objects on
>win95/98
>> or workstations ?
>>
>>
>> thanks
>> ranga
>
>

[ranga raghunathan]

this is bizarre -- i started this thread -and mark posted the first reply
- but the immediate reply below is by someone who has replied to this post
using my name !!! -- for the benefit of our anonymous friend, i reproduce
the kb article (relevant portion)- the article does not mention nt workstation
but only the nt or 2000 server

-- kb begins
SUMMARY
When using the Microsoft Visual Basic CreateObject function to create/return
a reference to an ActiveX object using the servername argument, the following
errors may occur:

Runtime Error '429':
ActiveX component can't createobject
-or-
Runtime Error '462':
The Remote Server Machine does not exist or is unavailable



MORE INFORMATION
The documentation for the CreateObject function does not mention that the
server referenced in the servername argument must be a Windows NT or Windows
2000 server.
--kb ends ---

as one can clearly see, the above line DOES NOT say Windows NT workstation
- it says nt or 2000 Server !!! .. so as to save our anonymous friend's valuable
time, i tested it and i could not create a remote object ON a nt workstation
from a 95/98 machine.
hope this piece of info saves some precious time for our anonymous poster.

thanks
ranga


"ranga raghunathan" <ranga1@msn.com> wrote:
>
>article 191121 says:
>The documentation for the CreateObject function does not mention the server
>referenced in the servername argument must be a Microsoft Windows NT Workstation
>or Server.
>
>For example, the following line of code should create and return a Microsoft
>Excel application object from the specified server, if the server is a Microsoft
>Windows NT Workstation or Server.
>
> Sub Test()
> Set xlObj = CreateObject("Excel.Application","\\MyServer")
> xlObj.Visible = True
> End
>
>I suggest that before posting a question you should read the documentation
>more than one time. It may sound a little bit rude
>but try not to waste other people time.
>
>
>
>
>"Mark" <please.dont@send.me.mail-use.the.newsgroup> wrote:
>>I believe that client machine must have user-level authentication, ie)
be
>>part of an nt domain, or connected to an nt workstation machine. This is
>>found in the last (?) tab of the network panel.
>>
>>Then you must make sure that the class you want to invoke is allowed to
>be
>>invoked by remote users. This is configured using: dcomcnfg.
>>
>>I hope that this is right - I haven't used Win98 in a while .
>>
>>"ranga raghunathan" <ranga1@msn.com> wrote in message
>>news:3926a55c$1@news.devx.com...
>>>
>>> the CreateObject(progid,servername) function works only if the
>>> servername specified is a windows nt server or a 2000 server but not
a
>nt
>>> workstation or a 2000 professional workstation ..this is not documented
>in
>>> msdn library but there is a kb article on this - Q191121
>>>
>>> does anyone know of any other function to create remote objects on
>>win95/98
>>> or workstations ?
>>>
>>>
>>> thanks
>>> ranga
>>
>>
>

[Mark]

I definately know that you can create objects on Win9x workstations. Check
out the documentation for the dcomcnfg tool. You can point the server where
the class is to be instantiated, and then create a class normally in VB and
it won't know that it is being created on another machine. The caveat is
that the Win9x machine must have user-level authentication, as I said
before.

Mark

"ranga raghunathan" <ranga1@msn.com> wrote in message
news:393da45b$1@news.devx.com...
>
> this is bizarre -- i started this thread -and mark posted the first reply
> - but the immediate reply below is by someone who has replied to this post
> using my name !!! -- for the benefit of our anonymous friend, i reproduce
> the kb article (relevant portion)- the article does not mention nt
workstation
> but only the nt or 2000 server
>
> -- kb begins
> SUMMARY
> When using the Microsoft Visual Basic CreateObject function to
create/return
> a reference to an ActiveX object using the servername argument, the
following
> errors may occur:
>
> Runtime Error '429':
> ActiveX component can't createobject
> -or-
> Runtime Error '462':
> The Remote Server Machine does not exist or is unavailable
>
>
>
> MORE INFORMATION
> The documentation for the CreateObject function does not mention that the
> server referenced in the servername argument must be a Windows NT or
Windows
> 2000 server.
> --kb ends ---
>
> as one can clearly see, the above line DOES NOT say Windows NT workstation
> - it says nt or 2000 Server !!! .. so as to save our anonymous friend's
valuable
> time, i tested it and i could not create a remote object ON a nt
workstation
> from a 95/98 machine.
> hope this piece of info saves some precious time for our anonymous poster.
>
> thanks
> ranga
>
>
> "ranga raghunathan" <ranga1@msn.com> wrote:
> >
> >article 191121 says:
> >The documentation for the CreateObject function does not mention the
server
> >referenced in the servername argument must be a Microsoft Windows NT
Workstation
> >or Server.
> >
> >For example, the following line of code should create and return a
Microsoft
> >Excel application object from the specified server, if the server is a
Microsoft
> >Windows NT Workstation or Server.
> >
> > Sub Test()
> > Set xlObj = CreateObject("Excel.Application","\\MyServer")
> > xlObj.Visible = True
> > End
> >
> >I suggest that before posting a question you should read the
documentation
> >more than one time. It may sound a little bit rude
> >but try not to waste other people time.
> >
> >
> >
> >
> >"Mark" <please.dont@send.me.mail-use.the.newsgroup> wrote:
> >>I believe that client machine must have user-level authentication, ie)
> be
> >>part of an nt domain, or connected to an nt workstation machine. This is
> >>found in the last (?) tab of the network panel.
> >>
> >>Then you must make sure that the class you want to invoke is allowed to
> >be
> >>invoked by remote users. This is configured using: dcomcnfg.
> >>
> >>I hope that this is right - I haven't used Win98 in a while .
> >>
> >>"ranga raghunathan" <ranga1@msn.com> wrote in message
> >>news:3926a55c$1@news.devx.com...
> >>>
> >>> the CreateObject(progid,servername) function works only if the
> >>> servername specified is a windows nt server or a 2000 server but not
> a
> >nt
> >>> workstation or a 2000 professional workstation ..this is not
documented
> >in
> >>> msdn library but there is a kb article on this - Q191121
> >>>
> >>> does anyone know of any other function to create remote objects on
> >>win95/98
> >>> or workstations ?
> >>>
> >>>
> >>> thanks
> >>> ranga
> >>
> >>
> >
>