Hi all.
Figures, I've been able to install and manage some SEP 12.1.2 deployhments at customer sites, but at my own site, I can't get clients to talk to SEPM and I'm not sure why.
I have 3 client systems I'm working with and one SEPM server, all on same local subnet.
Clients:
- Win XP Pro, has been running Unmanaged SEP 11 for a long time
- Win7 Pro - fresh install
- Win8 Pro - Fresh install (with the KB2781197-removal workaround applied)
- 3 Win2008 R2 Enterprise servers (1 as the host, two as VM's within)
SEPM:
- Installed on 2008 R2 Enterprise server, which is a VM in a non-domain environment.
- VM host is also 2008 R2 Enterprise as mentioned above
Problem:
The Win XP and Win8 machines cannot communicate with SEPM. Under Troubleshooting in the client UI, it shows them as Never connected to the server (over port 8014).
The Windows 7 laptop CAN communicate, as can the host and VMs as well. Again, SEPM is in a VM for what that's worth.
The fact that the external laptop can do so should tell me that I don't need to worry about firewall settings etc for the VM running SEPM, right?
The SEPM install is compmletely default, I haven't even created any policies or anything yet.
Correction: After discovering this issue, I edited the default Firewall policy to include the Local Subnet as a blanket Allow All policy.
I ran SymHelp which I'm new to, which doesn't seem to test network communications issues since none of the feedback it gave seemed to relate to anything network-oriented. It was all local SMC services and so on. Actually I'll run it again and post results here.
So my question is this, how do I go about troubleshooting this one? A new Win8 system can't communicate, an old XP system can't, but a mew;u omsta;;ed Win7 can? All using the same SEPM intall package? (well, the XP was a 32bit).
Thanks all.