DNA Client installation - 2 issues

[bojo387]

Hi All,

Any inputs on the issues below would be very much appreciated.

Issue # 1:

A. DNA Server: DNA 5.5 SP3 on Windows Server 2003
B. DNA Client: Windows XP SP2
C. Other info: Same network, same domain, using same windows account which is a local admin on both client and server.
D. Issue encountered: "_IsServiceInstalled function call failed"

This was an old issue during DNA 5.0 and fixed with a service pack so I assume the latest version would have this fixed but probably not in my case?

This was also from the same knowledge base article: "In certain configurations, D.N.A. client installation will fail when there is more than one item in the “Installed Services” dialog box.
The error message that D.N.A. will show is “_IsServiceInstalled function call failed.”"

Does anyone have any input other than the above?

Issue # 2

A. DNA Server: DNA 5.5 on Windows Server 2003
B. DNA Client: Windows XP SP2
C. Other info: Server is on a domain, client is on a workgroup and both are on different network segments. I can ping the server and map the DNA_S folder to the client. For the account work around, I created a local admin account on the client which is the same as a local admin/domain user account on the server and allowed me to do the folder mapping.

D. Issue encountered: Running the client installation, I still get the "Remote Connect Registry" error.

Any suggestions?

Also, can anyone list the ports that DNA uses between the server and client so I can have the IT side of the customer check both segments whether there is any blocking done on their network?

Thanks in advance!

 

[bojo387]

bump!

 

[parnum]

DNA uses named pipes

TCP 139 and 445
UDP 137 and 138

Can you access via regedit the server registry from the client, and also to the client from the server?

have you got antivirus/firewall in place, can they be switched off during install?

best parnum

 

[bojo387]

Thanks parnum. I will have the ports checked by the 2 sides as well as make a test regarding remote registry access.

There is no firewall on both the server and client but I'd have to check on the antivirus. I'll update this thread once I have more info.

 

[bojo387]

Issue #1, I tried but could not replicate the error so I am at a loss since the knowledge base article does not apply in this case. It should have been fixed in the newer versions anyway.

Issue #2: Well, I set-up two network segments and a domain controller + a workgroup PC. In our lab, I was able to install DNA client after making sure the ports specified were open and disabling some entries for clients in the domain controller's Domain Security Policy.

On the workgroup client, I can get OWS to work and can search the directory but both DMG and EMG cannot connect and have errors.

DMG: Failed to connect to directory database

EMG: Cannot connect to database server

Anyone ideas what I need to check?

 

[parnum]

This is usually a SQL ODBC issue, make sure your ODBC client connection into server works by testing on a dummy ODBC client connection into Server.

best parnum

 

[parnum]

Also check TCP/IP and named pipes are enabled in ODBC config on server as they are disabled as default. If you use SQL Express connect with instance name SQLExpress not just SQL server name.

best parnum

 

[bojo387]

Both issues were resolved.

For Issue 1: I played with the domain security policies and it worked. but I don't recall which entry made it work.

For Issue 2: Thanks Parnum, after allowing Named Pipes and TCP/IP in SQL Config, everything was fine in my lab set-up.

But on the customer site, it is a nagging issue as below:

DNA Server (in domain) is on different network segment with proposed client PC (workgroup). I can ping the server, telnet to ports 139 and 445 to the server from the client but not the other way around. I can access shares from the server including the administrative shares and DNA Client installation files but still get this when I try to install DNA on the client PC:

Remote Connect Registry

Remote Computer, <Server name>, cannot be connected.

I cannot also do a remote registry edit/access from the client to the server. The customer's IT department insists if I can access the server share and invoke the installation from there while at the client, that pipe created from client to server should be enough and they don't need to open it both ways. I have a hard time debating this with them as I've said, if I can't see the client from the server, how am I guaranteed all communication gets through? They won't allow me to run any trace as well as the client is a bank and have VERY strict rules.

Are they correct? Has anyone encountered this? This has gotten utterly frustrating jawing back and forth.

Thanks in advance.

 

[parnum]

"I cannot also do a remote registry edit/access from the client to the server."

You must be able to have permission to access the server registry from the client with regedit. The registry is written on the server and the client at client install, so you must overcome this as your next step.

best parnum

 

[parnum]

Also, if you have not already, request another mapped drive from your client to the system root drive (c:\) not just the dna_s folder (so you have admin rights on the system drive and your dna_s share on maybe partitioned drive), this will give you admin rights on the server for the install (you will be able to run regedit from the client as a test here). This should be set to reconnect at logon, reboot after install and you must 1st time log in as admin account, if the pop-up DOS box registers the dll's you can unmap the drive and test your client. If it pops up and disappears, you have failed to register the dll's and still have a permissions problem with the account you have mapped the drives with.

best parnum

 

[bojo387]

Thanks Parnum. I have not tried mapping the system drive but did check if I can access the administrative shares such as "\\hostname\C$" which I could.

I will try to recreate the scenario in my lab though I know it is a long shot trying to figure out what else they've restricted in between the two network segments.

 

[jkestens]

Hi bojo387,

I've got the same problem.
Did you tried it in your lab already?

Thanks,