Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 14 NOV 1997 03:48:11PM Matt Thomas-Googins wrote:

We have workstations which need IPX & TCP/IP loaded, and both protocols loaded on the NT Server… and were suffering really bad reposnse time in Ceridian/OpenInsight. When we de-installed IPX from the workstation, perfromance improved greatly. However, we need IPX, so we reinstalled it on the workstation, and predicatbaley, performance suffered.

So, we de-installed IPX from the server, and again perfromance improved. When we re-installed IPX on the server (because we need it there for another application).. perfromace stayed OK. Our thinking at that time was that the server now had TCP/IP at the "top" of the protocal stack, and that the server and workstation were now talking only IP.

At this point we celebrated, thinking we had licked the problem.

Unfortunaelty, for some unknown reason, perfromance has al the sudded gone to heck again. Our network people tell us there is no way to "tell" the application to exclusively "talk" IP to the server, or to tell the server only "only" talk IP to the application.

Any ideas?


At 14 NOV 1997 04:17PM John Duquette wrote:

Matt,

Although I do normally suggest to not have both protocols installed for performance I use both here so I do have some suggestions that you can try.

1) Be sure to use the Novell Client32 (current release for 95 is 2.12 I believe) Make sure on the workstations that you do not bind IPX to the Microsoft client.

2) Make sure that you have TCP/IP on the top of the protocol stack on the server

3) On the workstation that has performance problems, unmap the drive reboot and then remap the drive.

John Revelation

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/2351584a8be414e28525654f0072469b.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1