>>>BTW, is there any possible reason why would SQL server want to access the Web when it boots?
>>
>>Perhaps it want's to call home?
>
>That's what I'm curious about. If it is, I'll probably take the time to tweak the firewall to give it an illusion it's working for Robinson Crusoe. I may create a BottlesForMessagesHome database, and make it read-only ;).

Almost like setting up your own 'honey pot'!! ;-)



>
>>>Also, what is lsasrv.dll and lsass.exe (decribed very thoroughly as "LSA Executable and Server DLL (Export Version)") and why they keep trying to access the other machines in the network using the isakmp port (none of these names are mentioned in the w2k help)?
>
>>>Inbound UDP packet
>>>Local address,service is (0.0.0.0,isakmp(500))
>>>Remote address,service is (210.119.29.182,isakmp(500))
>>>Process name is "C:\WINDOWS\system32\lsass.exe"
>
>That's what I've found in my firewall logs. Too many times it comes from non-local address.
>
>>>Fox is the only reason I'm using Windows.
>>
>>Same for me... no need for VFP... no need for Windows.
>
>This sort of explains why was the VFP for Mac disontinued... they'd lose too many Windows users - many Fox users would switch to Macs :)

And, if they made it to run on the Max OS X (aka Darwin, aka FreeBSD) it would probably take very little to make it run on Linux.