Why we need to publish the NAV DB server?

shahul

Hi pals,

In windows 2000 professional, I have installed the NAV Database server
4.0 SP1 and accessed that DB server from different Clients on different
machines, without being published (to my knowledge, it is known that
publishing is allowed in server OS only). Without publishing with Active
directory, I have accessed the common DB from various clients.

What is the significant purpose of publishing with Active directory?

Could you please emphasize the differences between publishing and non
publishing DB server?

Thanks & Regards,
Shahul.
[/b]

lubost

When you use database authentification, you don't need active directory.

shahul

Thanks Lubost,

Without publishing the NAV DB server, windows authentication is also allowed here. I have tried to connect the NAV DB server using windows authentication and it works.

The machine in which NAV DB server locates having win2000 professional, it is not a server. Obviously there is no active directory component available here.

Noe: My machine exist in a network, where win2000 server available.

kine

The publishing into AD is just about possibility to see the server in server list. Nothing more. But as you know, you still can connect to the server when you manually enter the name.

shahul

Hi kine,

Thanks for your valid information.

I have loaded NAV DB server in windows Server2003 standard edition, and published into AD. But the server is not showing in the server list (File->open database -> Available Navision Database Server).

Where could I view the list?

Kindly clear my vision.

Regards,
Shahul.

kine

I never used that and I know that everyone who tried that failed. But this is theoretical "why" you need to publish it. Never heard that it is working... 8)

shahul

Thank you kamil.

Since I have tried to follow the NAV course material, they mentioned that we need to publish it.

Here the content in NAV courseware:
Publishing Microsoft Navision Database Server in a Network
In order for other server and client computers to be able to identify and connect with your Microsoft Navision Database Server, you must publish it in the network. Before you can publish a Microsoft Navision Database Server in the network, you must add a definition of a Microsoft Navision service connection point to the Active Directory. Microsoft Navision Database Server uses this service connection point to publish itself in the network and the clients use this information to locate the server and to find out how to connect to it. Only servers that have been installed as a service can be published in the network. To add a definition of a Microsoft Navision Database Server to the Active Directory, you must add a Schema Extension to Active Directory. This must only be done once for each forest of domains and domain trees, regardless of how many Microsoft Navision Database Servers are in that forest. When you install Microsoft Navision Database Server, a file called schemaXt.exe is copied into the folder that contains Microsoft Navision Database Server. Run this file to add a definition of a Microsoft Navision service connection point to the Active Directory. Starting up a Microsoft Navision Database Server (running as a service) will publish a service connection point using the definition that has been added to Active Directory.

kine

And as you can see, you need to do it in this order:

1) Extend the schema
2) Start the server, it will register the service in the AD

after that, check the Event log for possible warnings, errors or info about this. If the schema is not extended, there will be one error for each service start/stop about problems with registration into AD. If the schema is extended, these errors will not appear.

shahul

Yes Kamil,

I have followed those two steps already and tried. The Server name is not existing in the NAV server list, while opening the Database.

Kindly give me the path where I can find the Event log.

kine

Start - Control Panel - Administrative tools - Event viewer