PDA

View Full Version : FlashFXP kills Windows XP Pro networking


aaronpa
03-28-2003, 01:05 PM
I have no idea why, but without even USING FlashFXP, just the fact that it is installed kills networking on my Windows XP Pro machine. (WinXP Pro SP1, patches current as of 3 days ago)

This is using the latest build of FlashFXP (downloaded two days ago).

When the machine boots, I can logon, then open network shares, no problem. If I leave the windows open, no problem. If I close the windows, after about 15 minutes, I can't reconnect to the share. I have to either logoff and logon again, or reboot the machine.

After uninstalling FlashFXP, networking is back to normal, I can leave the machine on nonstop, then connect to shares at will with no issues.

Any ideas whatsoever? I love FlashFXP, especially the ability to schedule downloads, but I can't be logging off or rebooting every 15 minutes. That's bad even by normal Windows user standards.

If I can help troubleshoot this in any way, or if you need additional information, let me know.

Aaron

bigstar
03-28-2003, 03:12 PM
I'm not quite sure what to say... I've never heard of anything like this before.

Installing FlashFXP makes no changes to your system or network configuration, The installer merely copies over the files (all of which are installed into the \FlashFXP folder, creates the start menu shortcuts and assigns flashfxp to open .fqf files.

Have you tried re-downloading FlashFXP from our website?
http://www.flashfxp.com/download.php

Shark
03-28-2003, 04:33 PM
I have been testing FlashFXP with XP since it came out, and XP SP1 as well...

I have not noticed any such problems. I definatly use network and shares, etc everyday.

MidKnight
03-28-2003, 06:42 PM
same answer as shark, and i use flashfxp very heavy across a network, no problems

aaronpa
03-30-2003, 08:37 PM
Ok, after some additional use, I've figured out that I don't think it's FXP any more. I think it was just a coincidence that the problem occurred at the correct time to make it appear that FXP was at fault.

Now I'm trying the fix listed in this MS KB article. 297684 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;297684)

I'll let you know how it turns out.