RemoteServer.ComputerName = '192.168.33.1'

[Tomas Bahnik]

Is it possible, and it should be as I understand the meaning of
DistributedCOM, identify the computer with the registered server object by
its IP address (or a domain name). What about assigning TCP port. At a first
attempt it doesn't works.

Tomas Bahnik
Dept of Physics
TU Liberec

[Dan Miser (TeamB)]

Yes, you can do this. There is a bug in DCOM that will not allow you to
specify the IP address of the local machine, but even then you could use
127.0.0.1. Make sure you've installed TCP/IP properly and that you can ping
the server from the client that doesn't work.
--
Dan Miser
http://www.execpc.com/~dmiser

[Tomas Bahnik]

Dan Miser (TeamB) wrote in message
<01bdfdc7$23283a00$1e7f...@dmiser.manpower.com>...

But I am developing my 3T apps on the server. Inserting IP address into
ComputerName property of RemoteServer and turninig Connected to True gives
me a message "Operation not supported" (D3). I would like to compile this
IP address into client part of app. What seems to work is
1. leave the ComputerName empty
2. register server object on the client machine
3. set "run on this computer" in dcomcnfg on the client to IP address.
I would like avoid registering server object on the client side.

Tomas Bahnik

[Dan Miser (TeamB)]

?omas Bahnik <tomas....@vslib.cz> wrote in article
<70p7f7$nb...@forums.borland.com>...

> But I am developing my 3T apps on the server. Inserting IP address into
> ComputerName property of RemoteServer and turninig Connected to True
gives
> me a message "Operation not supported" (D3).
>

So you're developing the client app on the server machine (33.1), and
setting RemoteServer.Connected=true for the client application on the
server machine. If so, this is the bug I was talking about. It should be
fixed in NT SP4 (which was FINALLY released on 10/20!!!). However, even
without SP4, you should be able to specify the IP name with no problems.
Barring all of that, the method you describes should work fine.