Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

The remote server machine does not exist or is unavailable

Status
Not open for further replies.

fergve

Programmer
Aug 12, 2002
7
BR
Hei
I need your help!
I have a dll installed at COM+. (WINDOWS 2000 SERVER)
I export the dll to an application proxy and installed the package on the clients (windows 98).
But, When I create an instance in my VB code happened an error:
The remote server machine does not exist or is unavailable

My server has the Service Pack 3. What do I need to install on Server to resolve it?

thank´s ferg
 
the machines can obviously ping eachother?
Are they in the same domain?
Is there any type of firewall in between?
 
Hello
The net is an novell and there is a firewall for the Internet
The strange is that clients that are running windows2000 don't have this problem.
There is an update to windows98 to use Com+?
Or the problem is the Windows2000 Server?

Thank's ferg

 
The only OS that needs special setup/installation for DCOM is W95.

There are issues with accessing COM objects on a W2k/NT/XP server from a client machine so let me go through them

If you have a windows machine trying to access a resource on the server the server must trust the client. I'm working through similar issues where I am since they use novell I get "Permission Denied" error all the time.

So I assume that the firewall is not between the client and the W2k COM server.

What is probably happening is that the W2K servers are all members of the same windows domian and when you log into them you have a trusted relationship with the COM server but W98 is not secure and the W2K COM server might not trust them.

Goto
Security on Windows 95 and Windows 98-Only Networks
and
COM Security Frequently Asked Questions
 
Hello,
I don't know if it is a security problem
I have a Windows2000 client in the same Domain that can connect the Com+.
I heard that is necessary have the latest Microsoft Installer in clients (SDK plataform). Do you know about this?

thank's ferg
 
It might not be but it might.

Say you have a windows domain.

If you have your com server running a component under a non-domain account and try to access it with another non-domain account you will get a permission error.

Now I assumed that the proxies where successfully installed on win98

When you run the MSI on the 98 machines does it install without any errors?

You could use regedit to look up you component's entry and make sure it is pointing to your server properly.

then use the server name and ping it via a does command line. It could be a WINS resolution problem.
 
Hello
I installed the msi file in the client without problems.
Was creatted a folder named ComApplications with a dll file and a tmp file. In the tmp file there was the name of Server.
I think about a problem in the client...
The net is an novell and there is a WindowsNt 4.0 Server to login. This Windows2000 Server is only COM+.
Is there any DCOM configuration that I need to do in The Server?

thank's ferg
 
Hello
I tried to ping the Server from the client
The client found the Server, but it could not send the packages to the Server (0% Lost)
If there is a Wins problem, how can I resolve.
In the Server or in Client?

thank´s ferg
 
Hello
I try to ping the server COM+ in the client
The Server has found, but the client did not send any package. There was a timeout.
The rate was: (100% Lost)
What do you think about this?
If the problem is WINS, how I can resolve?
In the server or in the Client?

Thank´s ferg


 
You have a networking issue.
If the server was found but you have 100% data rate loss that means either there is a entry for the server in a DNS or the HOSTS file but there isn't an actual path to the server or your server is blocking ECHO requests.

WINS needs setup on both sides. You need a WINS Server like a DNS server, normally domain controlers do this and you need to set it up under network on 98. Often DNS is used for WINS resolution.
 
Hello
I detected that the Windows2000 Server has several IP's.
Is it a problem for COM+?
When I try to ping with the name server it has found, but the client can't send packages.

Thank's ferg
 
Does the Server actually have multiple IPs or is it just that the DNS or HOST file has multiple or the wrong IP?

I think Component Services will listen on all interfaces of the protocol(s) its been set up to comunicate with. Make sure that TCP/IP is one of them.

 
Hello,
The Windows2000 Server has multiples IP's. I think that there isn't mistake about this. Maybe I wrong...
But, how the application proxy try to connect with the server name, maybe the multiples IP's are a problem, don't you think?
I can to ping to another Windows2000 Server that has only one IP. The client send all packages to Server. Rate: (0% Lost)

What do you think?

thank's ferg
 
It could be a protocol issue. You should work with an administrator and disable all but 1 of the protocols. Try TCP/IP. Make sure only one TCP/IP address is active and make sure that the machine name via DNS or WINS is pointing to that IP address.

It really sounds like you have bad entries in your DNS server. I'm not farmiliar enough with WINS and how it maintains lists to talk about it much.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top