how to know navision server port?

leugim

hi all, a single question

we have some customers with two or more attain services in a server, one for demo database, to have a place "to test what happen if...", and another one for "real" data.

when we install the servers, we have to modify the services file in ..system32\etc directory, specifying the port for each service

the question is: how to know this port numbers from a pc? imagine you want to connect to both Navisions and you only have the server ip...

hmmm..... :-s :-k :-s :-k

Kowa

Create two shortcuts on the desktop with different targets

Target Example Real server
"C:\Program Files\Microsoft Business Solutions-Navision\Client\fin.exe" servername=192.168.1.9:3001

Target Example Test server
"C:\Program Files\Microsoft Business Solutions-Navision\Client\fin.exe" servername=192.168.1.9:3002

DigiTecKid

Kowa wrote:

Create two shortcuts on the desktop with different targets

Target Example Real server
"C:\Program Files\Microsoft Business Solutions-Navision\Client\fin.exe" servername=192.168.1.9:3001

Target Example Test server
"C:\Program Files\Microsoft Business Solutions-Navision\Client\fin.exe" servername=192.168.1.9:3002

You can also do this by editing the services file on each client. Check the Application Developer's Guide:

TCP/IP on the Server
TCP/IP is the default protocol in the Windows 2000 and Windows XP operating systems. The server program will use TCP/IP port 2407 as a default. If this port is occupied by another process, you can specify another port by making a new entry in the services file. The services file is normally located in the directory:
C:\Windows\systems32\drivers\etc
Open the services file in Notepad or any other ASCII editor and make a new entry in the services file using the following format:
<servername> 3001/tcp
Replace <servername> with the name of the server from which you start the server program, and 3001 is a free port number.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Note
If you make changes in the services file, you must make corresponding changes in the services file on all client units. Otherwise, the client will not be able to find the server program on the network.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


TCP/IP on the Client
The client program uses the WinSocket API. This means that the client program can run on any TCP/IP protocol that uses the WinSocket API. When the client program runs on Windows 2000, or Windows XP, the TCP/IP protocol included with Windows can be used. If you have changed the TCP/IP port for the server program, you must make the same changes in the services file for each client. This can be done in the same way as described in the section called "TCP/IP on the Server."
If you are not running Domain Name Service then you will also have to edit the hosts file on all the clients. The hosts file, is normally placed in the same directory as the services file:
C:\Windows\systems32\drivers\etc
Open the hosts file in Notepad and make a new entry as follows:
x.x.x.x <servername>
Replace x.x.x.x with the server's TCP/IP address, and replace <servername> with the name of the server from which you start the client program.

leugim

ok... i think i didn't explain the question correctly... [-( of course updating services in clients it works correctly and there's no problem

think you are a single user and you don't have access to the server. your system administrator is on holydays, touring around bahamas or some other paradise with your pretty-blondy-and-so-sexy ex-girlfriend ... and nobody knows which port uses Navision server. you only have a desktop shortcut and .zup file has no data. it seems like hell (or heaven, it depends... O:) )

i was thinking about some utility like a port scanner o something like that...

regards

Arhontis

Hi,

There are some applications that can scan a remote computer for the open ports...

I have used some of them sometimes to determine such info when I was having problems with Business Analytics...

You could search for freeware remote tcp port scanning on the net...
You enter the remote server name or ip address and the range of the ports to scan and it results the status of the ports...

I hope this helps...

aci

Start a Command Prompt window, then type "netstat". This program comes with all versions of Windows. It will show you all TCP/IP connections and the ports they are using. When you execute it at the client, you would know which server IP and port number you are actually connected to.

Type "netstat /?" to see all options.

David_Singleton

Arhontis wrote:

Hi,

There are some applications that can scan a remote computer for the open ports...

I have used some of them sometimes to determine such info when I was having problems with Business Analytics...

You could search for freeware remote tcp port scanning on the net...
You enter the remote server name or ip address and the range of the ports to scan and it results the status of the ports...

I hope this helps...

I haven't actually tested this in the nexest version of Navision, (last time I checked was ver 2.01) but...

In those versions of Navision if they deteceted a port scan, the server would shut down as a security precaution. We found this from a clinet that routinely once a week did a systematic port scan of their internal network to detect potential security breaches. When we asked Navision they confirmed this, but would not elaborate.

But seriously, if your IT guy goes on vacation and the comany can not run, then you need a completely redesigned IT strategy. I know it happens, but hey what if they guy got hit by a bus?

Arhontis

Good info David, thanks for sharing...

In Nav database server 3.70.A and above I hadn't found any such problem, even if I had run remote port scanners...

David_Singleton

Arhontis wrote:

Good info David, thanks for sharing...

In Nav database server 3.70.A and above I hadn't found any such problem, even if I had run remote port scanners...

My personal belief was that it was not because of the actual port scan that the server died, i.e. I don't believe that it was a security thing. I am more inclined to hting that it was because the server interpreted the port scan as a Bad Packet. In older versions of Navison the server would shut down if they detected a major corruption on the network, and that does not happen anymore.

So I am glad to hear that it does not occur any more, it was quite an annoying "feature".

Arhontis

Maybe you are right and that is why:

"When we asked Navision they confirmed this, but would not elaborate"