Thank you very much Leonid. This is excellent information to get me on the
right track. I showed your response to a Microsoft MVP over in the OneCare
group. He agrees that it's a port issue. I sure hope this is resolved! I
will read some of your links, and see what I come up with!
Thanks again!
"Leonid S. Knyshov" wrote:
> Escalate your case to someone who is familiar with enabling custom ports on
> OneCare. I don't know the OneCare product, but I do know that BCM SQL server
> runs on a non-standard port. Don't even mention that this has to do with
> SQL. Focus on unlocking that particular port, which is 56183.
>
>
http://support.microsoft.com/default.aspx/kb/823938 - this is how we get BCM
> to run in non-standard configuration.
>
http://support.microsoft.com/kb/901164 - specific instructions about BCM
> troubleshooting related to SQL and the srvnetcn.exe tool that is mentioned
> in the previous article.
>
> This information is valid for BCM 2003. The situation may have changed for
> 2007, but I haven't tested any of that on 2007 yet.
>
> P.S. Symantec's corporate line of products that is descendant of Intel
> LanDESK Antivirus is good. Their consumer stuff is something I uninstall
> immediately. I certainly wouldn't want to go through that agony again.
> --
> Leonid S. Knyshov, CEO
> Crashproof Solutions, LLC -
http://www.crashproofsolutions.com
> MCP Exchange 2003/Small Business Server 2003
> Microsoft Small Business Specialist Partner
> See the tips and tricks section on my website for video tutorials on BCM
> Send a smile to Microsoft (Office 2007 Beta feedback tool)!
>
http://tinyurl.com/m4omy
>
>
>
