DNA Client question

[Cerdito]

Hi all,

Our helpdesk has access to our MD110 (BC10) via a DNA client PC. For some reason it needs to map a couple of shared drives on the DNA Server before Extension Manager (v10.1 DNA 4.1 SP6) will work. The server and client are both NT boxes which we are upgrading soon to 2003 server and XP respectively.

I can't work out what information is needed from these shared drives, would it be something to do with the SQL database?

Bearing in mind we will be re-imaging the server and client with DNA 5.2, will we need to map to the shares again (and keep the information in them at the moment)?

Thanks

 

[rfpui]

Hi
Similar problem was described thread806-882935
send me e-mail
wich version of BC you have?

 

[rfpui]

Sorry
Which version of BC you have

 

[Cerdito]

BC10 is the version I have

The client is mapping the drive 'DNA_S' on the server PC

 

[rfpui]

I have not my laptop now and I need 2 hours to look DNA Installation Manual to check that DNA 5.2 support BC 10. If yes it is good solution to upgrade DNA.

 

[rfpui]

From manual
D.N.A. 5.2 Application Suite is compatible with:
1) Microsoft Windows NT Server Version 4.0,Windows 2000 Server, and Windows 2003
When using Windows 2003 for the D.N.A. server, Windows NT 4.0 clients are not supported.


2 Ericsson MD110 PBX releases BC10, BC11, and BC12.1


And from me
DNA 5.2 not suporrted MD 110 BC12

 

[rfpui]

or you can try use HotFix 802 for DNA 5.0 SP8a
I know that its work with DNA 4 and Win2000 server
and I don't know how it work with DNA 4 and 2003 server

 

[Kressmark]

Hi,

The reason that you need to map some drives to get the DNA client going is that the client uses named pipes. If both computers are on the same domain this is generally no problem. However, if one computer is in a different domain or workgroup even you can just map any drive to open the connection for named pipes. You will notice that the first time you map a drive Windows will ask for username / password, but for the second attempt this is not needed any more - the pipe is open.

If you keep the same domain / workgroup configuration you probably need to do the same mapping again.

For more information about which services are using named pipes or not, see the DNA technical guide topic "D.N.A. Port Assignments"

/mk

 

[rfpui]

hotfix 802

Fault Corrected

The following fault has been corrected:
DNA Clients cannot connect to DNA Server when running Windows 2000 SP4 because the name pipe connections are cleared by W2K SP4.

 

[Cerdito]

ah brilliant Kressmark, I think you're right on the money there. The helpdesk client is in a different building across the city to the DNA Server they are connecting to so are on a different domain. This makes sense