Hi We have customer using Attain 3.60. Recently a new client has been installed. But when the client tries to connect to the server, the follwoing errors pops up 1) when the server name is specified then ‘The TCP/IP connection …’ 2) when the IP address is put then ‘The Server & Client do not have the same Program version Number’ But the fact is that there are installations done earlier and have been running succesfully. several times we crossed check the Hosts, Services files, and also reinstallation of the client…but still the problem persists… Operating system - win 98 and also when we ping the IP address its normal, but when the server name is pinged it says unknown host. whatz that am missing? thanks in advance MK
The subnet mask of client may not be matchingwith the servers’s subnet mastk in the TCPIP Properties of the network. Cheers
hi Girish thanks for the answer , but the subnet mask is same. MK
You must have the same version in both the client and the server.
Hi Naji same version of what ??? If you are talking about navision version then it is 3.60 and 3.60 on server and client. we do have a Navision Financials installed on the server, but on the client we did not install any Navision Financials version. But as i said earlier all the prior installations are working properly…it is only with this new system we hv a prob… cheers Mk
Ok, things to check: If the server has a different navision server executable version than the client it won’t connect and give you an error about the different versions. If the server is having two different servers installed check that you’re not connecting to the financials one. Usually when you setup two versions on the same server you setup the hosts and the services files on that machine, and the clients have to have the same port used for connecting to the server (or it will try to connect to the default port, that may be used by the financials server). If your ping to the server works fine but when you use the name it doesn’t, try the following: Go to a computer where it connects fine. Check if the services file contains a line whith the same name as the server you’re connecting to by name and take a note of what port is setup for that server. Go to the computer where you’re having the problem connecting. On server name, enter the ip address instead of the name followed by the port that was setup on the other computer for connecting, as example, if your server ip is 192.168.0.1, and the port is setup to be 2456, you’ll enter as server name: 192.168.0.1:2456 Try to connect. Also check that on the options (on the navision client menu)that you’ve setup the client to connect using tcp/ip (usually it was coming by default to connect using netbios).
Hi Thank every one for the answers and suggestions. the problem is solved. Infact it was misplacing of the host file in a different directory by the customer that caused the problem. thank u again regards MK
We got the same error now. But the fun part is that when you click (trying to login) some times… usualy four times… we get connected to the database. And we can work as it never happende. Until next time we open the client. Then we’re back to the magic four times 
Anybody found anything like this and found an answer to it?
quote:
Originally posted by Frodio
We got the same error now. But the fun part is that when you click (trying to login) some times… usualy four times… we get connected to the database. And we can work as it never happende. Until next time we open the client. Then we’re back to the magic four timesAnybody found anything like this and found an answer to it?
We see this problem too. Our “strange” happenings are; 1. occasionally it will let you straight in without showing the “version error” 3 times in a row. 2. appears to be ok first time if you delete the zup file before trying. 3. only happens with windows authentication. Database Authentication works fine. 4. opening the server with the IP address and port number still gives the intermittant “version error” messages… but then again, if you OK the error 3 times it then lets you in. Help! Regards, Tim Simmonds
I experienced a similar error last week when installing a new server and client. The server was 3.60 and the clients were 3.60a. Are you running the database server as a “service” I went in and stopped the service reintered my startup parameters and restarted the service, and we have never had the problem again. Good Luck