| Bug# |
Discovered |
Description |
Impact |
Fixed |
| 018 |
1.05sr1 |
This bug is limited to Windows XP with Service Pack 2
Microsoft has made some changes to the TCP/IP stack, which limits the number of unconnected outbound connections than can be made instantly to 10 (see here). Because DomainScan can scan more than 10 devices at the same time, the change may affect and crash DomainScan if the option Abort if ping fails is disabled, because DomainScan, in these situations, will try to connect, even if ping fails, and therefore create incomplete open outbound connections.
Workaround: Leave the Abort if ping fails option on (which is the default option). |
Program crash |
1.1 |
| 017 |
1.05sr1 |
Both the Ping Tool and the Preferences dialog have been assigned the same short cut key (ctrl+p). Because of this, the Preferences short cut doesn’t work. |
Annoying |
1.1 |
| 016 |
1.05 |
Due to a critical file lock present in both Client and Service, DomainScan will not run both modules at the same time. The module that is loaded first will continue to run, but the other module will fail to load, and terminate execution. |
Critical |
1.05sr1 |
| 015 |
1.04 |
Some tools close when DomainScan refreshes its database view. This is the basic fail-save behaviour, but too many tools use that behaviour when its not necessary
Note: The bug only affects databases that are mounted across the network |
Annoying |
1.1 |
| 014 |
1.04 |
DomainScan Service will, at the very first run, create a backup of the newly created database |
Annoying |
1.05 |
| 013 |
1.04 |
When ’List detected users’ is selected in the computer information window, the wrong member may be listed if a domain user and a local computer user has the same username (i.e. the local user may be shown instead of the domain user and visa versa) |
Annoying |
1.05 |
| 012 |
1.04 |
After a service downtime, the downtime was not subtracted from computer and user uptime calculation. Therefore computers may appear as being online more than 100% |
Recoverable
database
corruption |
1.04sr1 |
| 011 |
1.03 |
Downtimes are not subtracted from the service online counter - so the service always appear as being online 100% of elapsed time since installation, even when the service has been offline |
Annoying |
1.04 |
| 010 |
1.03 |
The online time indicator may not be correct |
Annoying |
1.04 |
| 009 |
1.02 |
The scan engine may lock up, and never complete |
Critical |
1.03 |
| 008 |
1.01 |
The computer and user counters doesn't update while DomainScan is minimized to the system tray |
Annoying |
1.02 |
| 007 |
1.01 |
The 'GH Online' component links to the old website, and that link is dead |
Program misbehaviour |
1.02 |
| 006 |
1.0sp1 |
The 'Service Setup' panel is buggy on Windows 2003 based computers |
Program error |
1.04 |
| 005 |
1.0sp1 |
The DomainScan Engine stops working after June 1st, due to fact that the expiration date from the release candidate was still active |
Critical |
1.01 |
| 004 |
1.0 |
Computer records are (seldomly) created even though there are no apparent changes |
Database pollution |
1.0sp1 |
| 003 |
1.0 |
Warnings are issued (to log and SMTP), even though there are no warnings |
Program misbehaviour |
1.0sp1 |
| 002 |
1.0 |
‘To many logins’ warning texts are not correctly formatted |
Annoying |
1.0sp1 |
| 001 |
1.0 |
Sometimes, DomainScan Client creates a 0x00000018 warning, and the program stops working |
Program termination |
1.01 |
