OfficeScan Server v10 SP1. Clients are Windows 7 Prof. Windows Firewall is enabled; OfficeScan f/w is not installed on the clients. The clients are AD members, Win 7 network profile type is "Domain".
Problem: When OfficeScan is installed on the Win 7 client, the Windows Firewall incoming rules get an entry for the OfficeScan Listener, on the correct port. The network profile type for the OfficeScan incoming f/w rule is initially set to "Domain", which is correct. With that setting, the OfficeScan server can communicate with the client and shows the client's status as "Online". But after the client reboots, the incoming rule for OfficeScan changes its profile setting to "Public". At that point the OfficeScan server can no longer initiate contact with the client and shows the client as "Offline". If the client manually changes that f/w rule's profile setting back to "Domain" then things work until the next reboot. The setting then reverts to "Public" again and it's broken.
What is going on here? Is Windows making that firewall setting change, or is OfficeScan doing it? Note that the client's network settings are for the "Domain" profile, confirmed before and after rebooting, and all other apps & drivers are fine.
I have a trouble ticket open with Trend but I'd appreciate anyone else's input. Today I had to force a bunch of users to reboot, twice, to update their client and thought it was fixed, and now the problem is back again. I need to get this fixed and stop bothering the users with this issue and know the a/v is working right. Not to mention I have other things I'd rather be working on. ;)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Trend Micro is now officially claiming this is not their problem and that nobody else has reported it to them. Meanwhile I've gone through our Group Policy settings etc. very carefully and cannot find anything that would account for this problem behavior occurring in our environment, and only to OfficeScan.
Here's what I've come up with that seems to resolve the problem for us:
In the Advanced properties for the Trend OfficeScan Listener incoming firewall rule, Interface Types, Customize. The default setting is "All interface types". If I change it to "These interface types" and select *only* "Local area network"; And change the network profile for the rule to "Domain", and apply it, the rule sticks and does not change across multiple reboots of W7. The OfficeScan master server shows the W7 client as "Online" and can push out updates to the client.
More testing going on but this seems like a reasonable solution.
Business Accounts
Answer for Membership
by: IT-Monkey-DavePosted on 2009-11-10 at 14:25:14ID: 25790575
Nobody has any ideas about this? I've been going back and forth with Trend Micro, and they're adamant that this is a Windows problem. They pointed me to some MS Technet articles discussing problems with network adapter profiles changing to the wrong type. That isn't what's happening here. My NIC's profile is set to "DOMAIN" and it remains on "DOMAIN" at all times. All my installed apps that require firewall settings have the correct profile type selected.
But the incoming rule for OfficeScan Listener changes from "DOMAIN" to "PUBLIC" at every reboot, and from then on the OfficeScan Server can't talk to the OfficeScan Client.