Lance, I fought with one today XP, SP2. I ended up slowing the NIC down to
10 Full and got it to 30 sec. I'm including an excerpt from a previous post
that I used to try to correct the problem, maybe some of this will work for
you. If you fix it let us know what worked!
--------------------------------------------------
Summary XA LOGINS and Performance are slow
Book Vantage General Information
Page 113.1923MPS
PROBLEM DESCRIPTION: Logins into Vantage/Vista is slow.
Through experience we have found the following login times to be reflective
of different network or workstation issues:
--> Normal login on a perfect network is about 2 to 10 seconds.
--> If it takes 15 seconds to 1 minute, typically this is Virus
--> protection
software that is simply doing an active scan of all files as they are being
passed to the workstation.
--> 1 to 3 minutes, can be menu OCX handles are pointing to an old
--> Vantage
share that was recently disconnected.
--> 3 to 5 minutes, is usually either the NIC or a SmartSwitch that is
--> set
to "Autodetect" everything from line speed to duplexing.
XA500
XA510
XA520
XA600
XA610
PROBLEM RESOLUTION: Things to Check....
* Virus checking will cause logins to range from 45 seconds up to 3
minutes. Make sure at both the server and workstation exclusions have been
entered into the virus checking configuration. Exclusions should be at
Minimum the following files: Prowin32.exe, Vantage.* and c:\vntgwk52.
The maximum and easiest exclusion is to have it exclude the "V" mapped drive
completely as well as the local working directory c:\vntgwk52.
* Check the server for an Open-GL screen saver. You should use either a
blank one or select 'none' on the server. Open-GL screen savers occupy heavy
percentage of the processor's time, which can cause application performance
to suffer greatly. I've seen a customer exihibit similar characteristics
and they were running an Open-GL screen-saver.
* Only if you are upgrading from a previous version consider this step. This
could be because an old Vantage shared drive was just disconnected. Run the
Unregocx.bat file from the problem workstation.
At the command prompt, type: V:\Vantage\Unregocx X (V being your new
Vantage drive map and X being the old drive letter or letters) Do not use a
colon after the drive letter.
Run this command changing the last drive letter at the end of the command to
reflect all old Vantage mapped drive letters used in the past.
* If the Server is new and the mother board is made by Quantum Designs,
version "PlatiniX 4X" you MUST update the BIOS. Manufacturer is aware of
the problem and has the update available.
* Confirm that NT has been installed in such a way that both processors are
actually being used.
1. At the server, select Start -> Programs -> Admin Tools -> Windows NT Diag
2. Select the System tab. You should see CPU 0 and CPU 1 listed. If only
one is displayed, then NT has been installed improperly.
* Look at is NT Performance Monitor. Do Ctrl-Alt-Del (once only!!!) and
then select the Task Manager button -> Performance tab. What is CPU usage
amount? (%)
* What is the Total MEM usage indicated? What is amount listed Total
Physical Memory? If MEM Usage is greater than Total physical memory, then
paging memory is being used, which would slow down the system. Verify the
"# of Database Blocks" or the -B is being used or is high enough to push the
database up into RAM. See doc on -B.
* Verify in the -spin parameter of: -spin 2000 has been entered. This
tells Progress to utilize both processors.
* NETWORK ISSUES: Try logging into Vantage at the Server. If the response
is fast, you are dealing with a Network issue.
* Check the actual switch. In some cases the Switch will be detecting the
hubs as full duplex devices (there are such a thing as full duplex hubs, but
perhaps yours is not). If you have a second switch, try plugging the hubs
into the second switch, where it might correctly detected as half duplex.
This actuall ended up solving the problem for one customer.
With a properly configured Ethernet network and the right hardware,
you might achieve 20 percent or so better network transfer rates when using
full-duplex as compared to half-duplex.
However: it is very common for people to have misconfigured or incorrect
network hardware and receive very poor performance with full-duplex.
Throughput is not zero, but can be very low.
Full-duplex Ethernet is point-to-point. To get it right, both ends
of the Ethernet segment must be connected to full-duplex capable devices and
both ends must be configured as full-duplex. If one end is half-duplex and
the other is full duplex, then the network may work part of the time and
packets may be dropped part of the time, resulting in a large number of IP
and TCP/IP retransmissions.
If your computer is connected to a switch, it must be a full-duplex
capable switch. If your computer is connected to a hub, you cannot use
full-duplex at all.
* Check the NIC cards. Are they they same or different? In the properties
of the card there is an "Advanced" tab and under that is a bunch of things
that most usually ignore. There is a Line Mode that defaults to AutoDetect.
For some reason the card might not be autodetectiong the right mode so set
it manually to Full-Duplex or Half-Duplex depending on the Hub or the
Switch.
Also in the Advanced Tab is line speed and the default is autodetect. You
might want to check that also.
CAUTION: changing the NIC card on server, may require a reinstall of
PROGRESS due to The MAC address encryption, plan this for off time.
* "Maximize Throughput for Network Applications" this can have a big impact
on improving performance.
To change this setting, go to [Start] --> Settings --> Control Panel
--> Network. Click on the "Services" tab, then on "Server". Next, click
on [Properties]. Click on the radio button for: "Maximize Throughput for
Network Applications". This does require a reboot of the Server to take
effect.
* Win2003 Server w/ Wins and Active Directory -- Win 2003 server with WINS
and Active Directory do not mix, similar to water and oil. Shut down the
WINS and see if the lights on the switch dim as the WINS polling is no
longer running.
================================================
Here are two customer testimonials regarding NICs, HUBS and Switches and the
changes they made with their outcome.
"You might find the attached document interesting. It details some of the
settings related to integration of a CISCO 2924XL switch and a
Intel-Pro-100+ Server adapter.
My basic problem today was that my CISCO switch was programmed to force
the 2 ports into a 100-full duplex mode while I had the Intel card set to
Auto. The Intel card defaulted to 100-half duplex. Forcing it into
100-full mode helped considerably!
Note, however, my final comments about using single port cards vs dual
port cards. Given the possible bridging conflicts that might occur between
a RAID controller and dual-port card I can see no reason for taking the
risk. On the other hand I already own 2 of the cards."
"I changed my Intel Pro 100 server adapters from auto-sensing to Full
Duplex, 100bt... man what a difference!! average time to login went down to
10-15 seconds :) I also changed the Adapter team configuration from Adaptive
load balancing (on fail) to 'Fast EtherChannel'. Huge performace gains.
Thanks!"
"I asked several network admins about 100MB switches. Most seemed to
recommend keeping the clients at 10MB and just letting the servers and
switches run at 100MB. After experimenting some, I turned everything up to
100MB/Full-duplex. No problems, everything ran 10x FASTER!".
-----Original Message-----
From: Lance [mailto:lance02@...]
Sent: Wednesday, October 27, 2004 2:43 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Vantage slow
Hi -
We are running Vantage 6.10.511. For the last couple of weeks, it
has been slow in starting up for several people, but not all. Those
affected are running Windows XP, SP1. Windows 2000 users do not seem
to be slowed down. Also, only some of the Win XP users are affected,
not all. Typical login time is 15-20 seconds. On the computers
where it has slowed down, it now takes anywhere from 1.5-2.5 minutes
to login. Including, a long delay after you get to the login screen
and enter username and password. Any ideas what could be going on?
I have tried to uninstall any MS security updates added to one of the
affected computers, to no avail. Have also tried turning off virus
scanning, again with no luck.
Thanks,
Lance Ekum
Sentry Equipment Corp
10 Full and got it to 30 sec. I'm including an excerpt from a previous post
that I used to try to correct the problem, maybe some of this will work for
you. If you fix it let us know what worked!
--------------------------------------------------
Summary XA LOGINS and Performance are slow
Book Vantage General Information
Page 113.1923MPS
PROBLEM DESCRIPTION: Logins into Vantage/Vista is slow.
Through experience we have found the following login times to be reflective
of different network or workstation issues:
--> Normal login on a perfect network is about 2 to 10 seconds.
--> If it takes 15 seconds to 1 minute, typically this is Virus
--> protection
software that is simply doing an active scan of all files as they are being
passed to the workstation.
--> 1 to 3 minutes, can be menu OCX handles are pointing to an old
--> Vantage
share that was recently disconnected.
--> 3 to 5 minutes, is usually either the NIC or a SmartSwitch that is
--> set
to "Autodetect" everything from line speed to duplexing.
XA500
XA510
XA520
XA600
XA610
PROBLEM RESOLUTION: Things to Check....
* Virus checking will cause logins to range from 45 seconds up to 3
minutes. Make sure at both the server and workstation exclusions have been
entered into the virus checking configuration. Exclusions should be at
Minimum the following files: Prowin32.exe, Vantage.* and c:\vntgwk52.
The maximum and easiest exclusion is to have it exclude the "V" mapped drive
completely as well as the local working directory c:\vntgwk52.
* Check the server for an Open-GL screen saver. You should use either a
blank one or select 'none' on the server. Open-GL screen savers occupy heavy
percentage of the processor's time, which can cause application performance
to suffer greatly. I've seen a customer exihibit similar characteristics
and they were running an Open-GL screen-saver.
* Only if you are upgrading from a previous version consider this step. This
could be because an old Vantage shared drive was just disconnected. Run the
Unregocx.bat file from the problem workstation.
At the command prompt, type: V:\Vantage\Unregocx X (V being your new
Vantage drive map and X being the old drive letter or letters) Do not use a
colon after the drive letter.
Run this command changing the last drive letter at the end of the command to
reflect all old Vantage mapped drive letters used in the past.
* If the Server is new and the mother board is made by Quantum Designs,
version "PlatiniX 4X" you MUST update the BIOS. Manufacturer is aware of
the problem and has the update available.
* Confirm that NT has been installed in such a way that both processors are
actually being used.
1. At the server, select Start -> Programs -> Admin Tools -> Windows NT Diag
2. Select the System tab. You should see CPU 0 and CPU 1 listed. If only
one is displayed, then NT has been installed improperly.
* Look at is NT Performance Monitor. Do Ctrl-Alt-Del (once only!!!) and
then select the Task Manager button -> Performance tab. What is CPU usage
amount? (%)
* What is the Total MEM usage indicated? What is amount listed Total
Physical Memory? If MEM Usage is greater than Total physical memory, then
paging memory is being used, which would slow down the system. Verify the
"# of Database Blocks" or the -B is being used or is high enough to push the
database up into RAM. See doc on -B.
* Verify in the -spin parameter of: -spin 2000 has been entered. This
tells Progress to utilize both processors.
* NETWORK ISSUES: Try logging into Vantage at the Server. If the response
is fast, you are dealing with a Network issue.
* Check the actual switch. In some cases the Switch will be detecting the
hubs as full duplex devices (there are such a thing as full duplex hubs, but
perhaps yours is not). If you have a second switch, try plugging the hubs
into the second switch, where it might correctly detected as half duplex.
This actuall ended up solving the problem for one customer.
With a properly configured Ethernet network and the right hardware,
you might achieve 20 percent or so better network transfer rates when using
full-duplex as compared to half-duplex.
However: it is very common for people to have misconfigured or incorrect
network hardware and receive very poor performance with full-duplex.
Throughput is not zero, but can be very low.
Full-duplex Ethernet is point-to-point. To get it right, both ends
of the Ethernet segment must be connected to full-duplex capable devices and
both ends must be configured as full-duplex. If one end is half-duplex and
the other is full duplex, then the network may work part of the time and
packets may be dropped part of the time, resulting in a large number of IP
and TCP/IP retransmissions.
If your computer is connected to a switch, it must be a full-duplex
capable switch. If your computer is connected to a hub, you cannot use
full-duplex at all.
* Check the NIC cards. Are they they same or different? In the properties
of the card there is an "Advanced" tab and under that is a bunch of things
that most usually ignore. There is a Line Mode that defaults to AutoDetect.
For some reason the card might not be autodetectiong the right mode so set
it manually to Full-Duplex or Half-Duplex depending on the Hub or the
Switch.
Also in the Advanced Tab is line speed and the default is autodetect. You
might want to check that also.
CAUTION: changing the NIC card on server, may require a reinstall of
PROGRESS due to The MAC address encryption, plan this for off time.
* "Maximize Throughput for Network Applications" this can have a big impact
on improving performance.
To change this setting, go to [Start] --> Settings --> Control Panel
--> Network. Click on the "Services" tab, then on "Server". Next, click
on [Properties]. Click on the radio button for: "Maximize Throughput for
Network Applications". This does require a reboot of the Server to take
effect.
* Win2003 Server w/ Wins and Active Directory -- Win 2003 server with WINS
and Active Directory do not mix, similar to water and oil. Shut down the
WINS and see if the lights on the switch dim as the WINS polling is no
longer running.
================================================
Here are two customer testimonials regarding NICs, HUBS and Switches and the
changes they made with their outcome.
"You might find the attached document interesting. It details some of the
settings related to integration of a CISCO 2924XL switch and a
Intel-Pro-100+ Server adapter.
My basic problem today was that my CISCO switch was programmed to force
the 2 ports into a 100-full duplex mode while I had the Intel card set to
Auto. The Intel card defaulted to 100-half duplex. Forcing it into
100-full mode helped considerably!
Note, however, my final comments about using single port cards vs dual
port cards. Given the possible bridging conflicts that might occur between
a RAID controller and dual-port card I can see no reason for taking the
risk. On the other hand I already own 2 of the cards."
"I changed my Intel Pro 100 server adapters from auto-sensing to Full
Duplex, 100bt... man what a difference!! average time to login went down to
10-15 seconds :) I also changed the Adapter team configuration from Adaptive
load balancing (on fail) to 'Fast EtherChannel'. Huge performace gains.
Thanks!"
"I asked several network admins about 100MB switches. Most seemed to
recommend keeping the clients at 10MB and just letting the servers and
switches run at 100MB. After experimenting some, I turned everything up to
100MB/Full-duplex. No problems, everything ran 10x FASTER!".
-----Original Message-----
From: Lance [mailto:lance02@...]
Sent: Wednesday, October 27, 2004 2:43 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Vantage slow
Hi -
We are running Vantage 6.10.511. For the last couple of weeks, it
has been slow in starting up for several people, but not all. Those
affected are running Windows XP, SP1. Windows 2000 users do not seem
to be slowed down. Also, only some of the Win XP users are affected,
not all. Typical login time is 15-20 seconds. On the computers
where it has slowed down, it now takes anywhere from 1.5-2.5 minutes
to login. Including, a long delay after you get to the login screen
and enter username and password. Any ideas what could be going on?
I have tried to uninstall any MS security updates added to one of the
affected computers, to no avail. Have also tried turning off virus
scanning, again with no luck.
Thanks,
Lance Ekum
Sentry Equipment Corp