My guess is that the problem was not related to the ports you listed, but rather to the fact that the security software was blocking all high ports. The various FoxWeb components use TCP/IP to communicate with each other, so it's important to place them in the exclusion list of any software firewalls you have installed on your server. The FoxWeb setup program automatically does this for the Windows firewall, but not for any 3rd party products. The processes that must be excluded are fwstart.exe and either fwserver.exe (if using the VFP run-time library), or the VFP executable specified in the FoxWeb Control Center (e.g. vfp9.exe).
Sent by FoxWeb Support on 07/19/2006 07:36:27 AM:
We have been having channel lockups for months now, but last month we removed norton corprate edition and installed mcafee protection pilot and noticed that it was stopping IRC information (ports 6666-6669) being sent from fwstart.exe and vfp7.exe. After added an exclusion for these exes to the protection server ALL channels have remained activate and if a script creates an error the channel restarts without a problem, this has been running for the last month without any problems. (I think it is fixed!!!!) no more channel lockups.
Sent by James Williams on 08/17/2005 10:19:18 AM:
Have done as asked and the channel restarts correctly. Will leave it running on these settings to see if the problem starts to re-occur.
Also forgot to mention that we also tried changing the port value in the registry so that the channels would start on a higher number but this did not change anything.
Will send to the foxweb registry key, but we have restarted the server now so it may not contain what you are looking for.
Sent by FoxWeb Support on 08/17/2005 09:54:17 AM:
We have found certain situations under which the channel status window does not display all running channels, which explains the situation under #2 below. However, this does not explain the original problem you describe. Please try the following:
Also, while the problem is in effect, please export the FoxWeb registry key and send it to us at email@example.com. you will need to rename the file to .txt (ar any other extention), so that it does not get blocked by our mail server.
Sent by James Williams on 08/17/2005 04:52:13 AM:
We are seeing this problem in version 3.0 & 3.1 where channels become locked and will not restart unless the server is restarted.
We are running 6 channels as services on windows 2003 sbs server with version 3.1.
Channels 1 & 2 lockout and do not show under showchannels and show in the registry as "_killed". These channels will not come back untill you restart the server.
We have tried to get these channels restarted by :-
1. Stoping foxweb and restarting.
2. Stoping foxweb and unchecking "run as service", this will start the remaining 4 channels, but under show channels will show channels 3,5,6 channel 4 is missing but seems to be running. (?)
Channels 1 & 2 remain locked out.
Only 4 vfp7.exe files show up in Processes under task manager.
The only thing that will sort out all the problems is a server restart.