Navision installed, can't connect, checksum error

conor

Hi all,

I've just installed Navision Server 4.03 on an XP pro machine. I'm trying to connect to it from another machine with Navision client 4.0 SP3 installed and I get the following error:

"The network is not functioning correctly. A 'packet' has been corrupted (a checksum error).
This error indicates that the network is not completely reliable. Please note how often this type of error occurs in the network. Contact your system manager if you need assistance."

Does anyone know what may be causing this?

kine

Check the network for possible problems. May be some switch is not working correctly.

conor

Thanks for your response.
I moved the machine to a different part of the building and it's now on a different switch. I get the same error. Any more suggestions?
Thanks.

kine

Change the PC network card.

conor

I uninstalled XP Pro and then installed Windows Server 2003. It's working fine now. Maybe Navision Server doesn't work on XP.

kine

You cannot expect good performance from server service running on XP, mainly if XP are optimized for interactive applications and not background services.

But it seems that it was problem of XP drivers for network card.

idiot

conor wrote:

I uninstalled XP Pro and then installed Windows Server 2003. It's working fine now. Maybe Navision Server doesn't work on XP.

Why not try uninstalled XP Pro & reinstalled XP Pro?
It might also have worked

fufikk

Hi,

I have Navision server (4.0 sp3) running on win 2003 SBS sp 2. With the TCPS net type client connects but with first logon the message: 'packet' has been corrupted (a checksum error) is displayed, you click OK and you can work. Later message never appears.
With TCP net type this message appears every time and logon fails.

Any ideas?

fufikk

After switching to TCP in server options and client as well the error message never appeared again.

BTW, there is a way to change net type settings without uninstalling/installing server: regedit and later HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/[servicename] the key contains net type setting as well as cache setting.

endjinn

Make sure the service account for the Database server service has rights in windows to the location where the FDB sits!