I have two computers of my own and now a customer's computer that has port 5003 being used or is somehow blocked. This is all beyond my experience level, but here's what I've done and identified... This port is reserved for FileMaker. The problems I'm having is keeping FileMaker from networking. - Here's what I've tried... I ran netstat -ona | findstr 0.0.:5003 and got the PID Then I ran a batch script with sc config [service] Type= own where [service] was each service in the PID Group Policy Client and Task Scheduler could not be broken out and after running the batch file, the port is associated with their PID The Task Scheduler database appears to be corrupt. I get an error "Task mcupdate_scheduled: The task image is corrupt or has been tampered with." I found a corrupt task in the Media Center and deleted it the rebooted. I still get an error message that it is corrupt (Media Center). Also, I didn't find any entries in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache. I can't find out any way to repair it but if the corruption isn't the problem, then I'm not concerned about it. (I have run CCleaner on both computers but this problem existed beforehand.) There are no entries in IPSec and I've never even known it existed before now so I assume it's unchanged. The firewall is off. I've used at least 3 different AV/security programs. All were cleanly removed and both of my computers seem very clean and stable. I don't know anything about my customer's computer. Both of mine are running Win 7. One is 64bit. The other is 32bit and was updated from XP SP3. So far as I can remember, I've had this problem since before Win 7. My computers are on a home network. My customer has the problem on a PC but he's running Win Server 2003. I can run other computers on the same subnet without any problems. Any guidance is GREATLY appreciated! Thanks!

Use netsh http://support.microsoft.com/kb/947709 Rgds Milos

Use netsh http://support.microsoft.com/kb/947709 Rgds Milos

Thanks Milos, That got me going in the right direction. I found that RPC had been assigned to ports 5000-5020 which appears to be standard under some circumstances. I couldn't tell what those circumstances were but changing the port range in the registry took care of the problem. Thanks again!