NAS cannot connect to server on other computer

DALE001

I installed a NAS successful on a computer but this NAS cannot connect to a Navision SQL database on another computer.

This is my test environment:
Computer A: pc with Win XP sp2, SQL server 2000, Navision SQL database 3.60. Clients are 3.70.
I installed a Navision client 3.70 on this computer and can connect without a problem to the database with windows authentication. I installed a NAS (3.70B) (same logon as I used to logon with the client). This NAS also connects to the database without a problem. I uninstalled the NAS after this test.
Data about the computer and database:
Computer name: PCBE01108
Database: BE20050910
Company: Test Comp

Computer B: Windows 2003 Server STD. I installed a client (3.70B) on this pc and can connect to the SQL database on computer A without a problem (with the same Windows authentication).
I installed a NAS (3.70B) on this computer and changed the settings in the registry of this service in order to connect to the SQL database on computer A.
When I restart the service I get 3 messages in the Event viewer:
The first message in the event viewer shows the ‘normal message’ indicating that the NAS has started. Also in the “Services” window the service is “Started”. After a few seconds when I refresh the event viewer I have 2 new warning messages. The first message is: “The PCBE01108 server cannot be found” and the second is: “The Navision Application Server PCBE01019-SQL could not initialize properly.

I’m 100 % sure that all settings like server, database, startupparameter, nettype, Company, Objectname are correct. There is no firewall running on these computers.
These are my settings in the registry for this NAS service:
Company: Test Comp
Database: BE20050910
Nettype: tcp
Servername: PCBE01108
Startupparameter: NASBE
Objectname: = my windows logon that use to connect from this same pc to the database on the other pc.
All other parameters have the default setting

I also have a SQL 2000 running on the second computer with another test database. When I change the NAS settings in the registry in order to connect to this local database, it works without a problem.

My windowslogon has almost admin rights and is a Super user in Navision.
I also tried with the administrator logon but it didn’t help.

I tried the same scenario on two very fast servers and 1GB switches (to exclude timing or performance issues) but the end result is also negative.

Thanks in advance for your suggestions.

kine

Try to set the NAS to connect directly to IP... may be that there is problem with the name resolving...

DALE001

I tried this also, but no succes.

thanks anyway,

DenSter

Did you change the windows user on the logon tab of the NAS-SQL service?

DALE001

Yes, I did. The NAS has the same windows login as the one that I use to connect to the database with a Navision client on that same computer.

DALE001

I found the solution:
instead of NETTYPE=tcp or NETTYPE=TCP, I left this parameter empty and now it works.
If someone knows the reason why, please let me know.

DenSter

That property is nothing but trouble. Every time I have a problem with NAS it is caused by the stupid nettype. I can't believe I didn't ask you about it.

NAS just needs a nettype to connect, just like you need at least two numbers to complete a calculation. Supposedly, it can handle tcp, tcps and netBios, but the only way I have seen it work is TCP. The funky thing is that in the NAS management console snap-in, you don't see the nettype for the NAS-SQL version and you have to set it in the registry or by using the command prompt.

When you install NAS, the installer sets the nettype to TCPS (you don't see this in the snap-in, but that is the default value), and needs to be TCP.

hawwa

how to set the nettype to tcp. I can't do it in the snapin

kine

1) You need NA 4.00SP1 to do that in snapin
2) If you have older version, you need to set it through registry or runtime parameters

DenSter

Look for a file called "w1w1atas.pdf" on your product CD. All the information you need is in there.