Re: Small Business Server - WMI issues

Alex_ACS <Alex_ACS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Here's the story. 4 different customers, 4 different servers. 3 of
them use Small Business Server, one uses Enterprise R2. I use a free
asset management/help desk/reporting system on all of them which
communicates using the WMI protocol, which we all know runs on
TCP135. The problem is that on all three of the SBS servers, the
asset management system doesn't want to communicate with HALF the
computers on each network. It recognizes them, authenticates with
them using a domain admin account, and roughly half of them on each
network just won't talk. I've tried adjusting WMI Control and DCOM
Config on the "unknown" machines that it won't communicate with,
netsh firewall set service remoteadmin enable, group policy firewall
exceptions, everything in the software's documentation, but nothing
works. One of these servers talks with 8 computers perfectly and 8
computers not at all.

The asset management program running on the Enterprise server detects
all 22 workstations on it's network flawlessly.

All the networks have Sonicwall firewalls, but they're out of scope
of the workstations (used as gateway) and TCP135 is passed through
anyway.

I already hated Small Business Server as compared to Enterprise, but
seriously... what's going on?

I suggest you try posting in microsoft.public.windows.server.sbs. I know
you've tested already, but I'm still inclined to think this is a firewall
issue (which you could address via group policy) - but to test that theory,
stop the underlying Windows service for the firewall on the problem
client(s) and test.


.

Relevant Pages

  • RE: RE: Front End/Back End communication
    ... communication between FE/BE via IPSEC then IF the front end server ... How likely is it that someone gets past your firewall? ... the FE and BE communicate in the clear. ... you against the real risk. ...
    (Focus-Microsoft)
  • Re: Bi-directional SOAP messaging possible?
    ... There's no way for a server to communicate back to the client asynchronusly in the case of a firewall. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: SMTP not working for External use: Cant Send Emails
    ... I have the port 25 mapped to the private ip address to the public ... > and on the firewall side...is your server allowed to communicate on the ...
    (microsoft.public.exchange.admin)
  • Firewall issue
    ... If there are two host and they are not able to ... communicate directly to each other due to a firewall in between. ... functionalities that server will be having?? ...
    (comp.os.linux.networking)
  • Firewall issue
    ... If there are two host and they are not able to ... communicate directly to each other due to a firewall in between. ... functionalities that server will be having?? ...
    (comp.unix.programmer)