Very slow file open if client machine is in AD Domain

[Emiliano Luca]

Hi,
Little premise: I’m a network specialist and I don’t use personally your software.
Actually I did not even well undestood what it is used for
BUT another department of my company is evaluating your software annd they reported me a different behaviour for client machines in Active Directory and machines not in AD.

To verify that I’m using a trial license and a 4GB local file (c:\test.fpd).
Well these are results :

– machine IN AD it takes about 25-30 minutes (half an hour) to open it.
in the meanwhile that client is totally freezed even task manager is unaccessible

– machine NOT in AD take 2-3 minutes (180 seconds) to open the same file

– machine that was IN AD (the one above) and then removed from AD (so same hardware, software, IP address, network and so on) 2-3 minutes to open the file

– machine that was not in AD and took 3 min to open configured in AD (same hardware, IP, etc) now takes 30 min to open the same LOCAL file

So the delta seems to be the AD configured or not on the client.
And that is why my colleagues came to network department and so to me.

I’ve used a network sniffer to monitor differences but I did not find any clue of what your software looks for and eventually is not able to find when AD is active on the client.

Do you have any other feedback with same issue as me ?
Do you have any recommendation, suggestion, test or any other action to find what the issue could be caused by?

Thanks in advance for your help

Regards

Emiliano

[Emiliano Luca]

Hi,
Little premise: I’m a network specialist and I don’t use personally your software.
Actually I did not even well undestood what it is used for
BUT another department of my company is evaluating your software annd they reported me a different behaviour for client machines in Active Directory and machines not in AD.

To verify that I’m using a trial license and a 4GB local file (c:\test.fpd).
Well these are results :

– machine IN AD it takes about 25-30 minutes (half an hour) to open it.
in the meanwhile that client is totally freezed even task manager is unaccessible

– machine NOT in AD take 2-3 minutes (180 seconds) to open the same file

– machine that was IN AD (the one above) and then removed from AD (so same hardware, software, IP address, network and so on) 2-3 minutes to open the file

– machine that was not in AD and took 3 min to open configured in AD (same hardware, IP, etc) now takes 30 min to open the same LOCAL file

So the delta seems to be the AD configured or not on the client.
And that is why my colleagues came to network department and so to me.

I’ve used a network sniffer to monitor differences but I did not find any clue of what your software looks for and eventually is not able to find when AD is active on the client.

Do you have any other feedback with same issue as me ?
Do you have any recommendation, suggestion, test or any other action to find what the issue could be caused by?

Thanks in advance for your help

Regards

Emiliano

[Bernhard Kantz]

Thank you for your comprehensive description of this strange behaviour. If you have specific questions you may send an email to support@weisang.com, since in the forum further inquiries could not be stated easily.

Referring to your problem, this is the first case of this kind we heard of. FlexPro stores it project databases (.FPD files) as compound files, and uses no network specific means (if no network license is used). Can you rule out any interaction maybe with anti-virus scanner and/or firewall trying to check for the integrity of the .FPD file in the AD case?

Huge project databases can also be stored as a structure of files and folders instead of a single compound file. You may test, if this changes the strange behaviour while loading the database.

[Author]

Posts