tcp econrefused NAV 4.0 SBS2003

logdog

Hello Navision Gods,
I have installed NAV 4.0 Database Server on a new SBS 2003 (I know SBS is not as good as straight server). I've added the line <server name> 18000/tcp in the services file found under c:\windows\system32\driver\etc and xx.xx.xx.xx <servername> in the host file found in the same directory and made duplicate entries in a Win XP Client. I can connect from the client interface on the server in Database Authentication Mode using TCP. The Navision Server service is started and netstat shows the port available but when I try to connect from the workstation I get this error.

" The Tcp/ip connection's 'host' is not answering (TCP/IP error ECONREFUSED) You can see how to make changes to your 'hosts' and 'services' files in the documentation for the network. Contact your system manager if you need assistance"

The Navision Server service is configured for TCP, and shows it using TCP when I run the server cmd from a prompt. The valid fin license is installed on both workstation and client.

Any help is greatly appreciated. Thank you in advance.

Logdog

DaveT

Hi,

Check the "Net Type" on the advanced tab of the client - set it to TCP and see if you can connect.

logdog

I have, repeatedly, I change the options tab first thing. I can connect via TCP from server desktop, but not from workstation, I have triple checked the HOSTS & Services file too. I even tried going to TCPS just to make sure. Do I need to join the domain to connect to the SBS? I am on the same subnet and network.

DaveT

Hi,

To eliminate the hosts as a problem - try connecting to the IP address of the server i.e. put the IP address in the the server name field. If this fails then try pinging the IP address from the dos prompt.

logdog

I get the same econrefused using the server IP address. Ping times are excellent, fast and I dont drop a packet.

DaveT

Hi

Are you using database or windows authentication?

I wonder is it a permissions problem?

logdog

There are windows authentications users and database authentication users but I created a Super w/ database authentication after I restored the database.

FYI it is a Native database not SQL. and thanks for the speedy replies

DaveT

Hi,

Sorry for the late reply - I think the site went down last night

The next suspect is a firewall or anti-virus software not allowing the connect. Try with these turned off.

logdog

Thanks for the ideas. I discovered that SBS2003 did not like the high number port that I was using. When I configured for a lower numbered port everything worked perfectly. Thanks again. You guys are the greatest.

DaveT

Glad to help and you can see it works both ways - now I've learned something new and not the hard way for a change