LOGIN issues

gsmmis2001
gsmmis2001 Member Posts: 2
edited 2000-12-14 in Navision Financials
I have a very simple question about logins.

I inherited a Navision 2.5 setup from previous MIS staff. I have noticed when users try to login the first time, the system seems to drag a bit (slow). After the user's initial login, there appears to be no performance degradation.

Does anyone know why this might happen?

I have also noticied users having a difficult time in general when trying to login before a specific time period (in this case M-F 8:00 am).

Also, are there any settings that might prohibit logins outside a certain time period?

Thank you, I'll sit down and wait for my answer.

Comments

  • Luc_VanDyck
    Luc_VanDyck Member, Moderator, Administrator Posts: 3,633
    There is probably a large cache defined on the Navision server. The first time Navision is started, this cache is filled with data. The larger the cache, the longer you'll have to wait the first time.

    Solution? A smaller cache, or create a macro that starts up a NF client at eg. 07:30 am.
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • mfabian
    mfabian Member Posts: 187
    I don't know if it's the same problem I encountered recently.

    Symptom: First time the user logs in, it takes about 30 seconds before the login screen appears. Application speed after this login is ok. Leave/restart Navision starts the program immediately.

    Solution: The TCP/IP address of the servername FINSERVER was not propperly defined in the DNS and therefore the server searched the internet first prior to searching it's own domains.

    Marcus
    Marcus Fabian
    m.fabian@thenet.ch
    +41 79 439 78 72

    [This message has been edited by fabian (edited 14-12-2000).]
    With best regards from Switzerland

    Marcus Fabian
  • brucem
    brucem Member Posts: 86
    Marcus has pretty much hit the nail in the head.

    when a TCP client starts it will look in the hosts file ( if it exists ) for a DNS entry for the server, if it doesn't exist the client will then send various requests out on the wire for an IP address of the client, depending on how the client is configured means how long it must wait until it gets a reply.

    The IP address is then stored locally in the workstation cache where it will remain if not updated for about 10 mins, after which the address will be reomved and the whole process will start again...

    Bruce

Categories