Hi Bill, thank you very much for that input. I have stopped and disabled the
Computer Browser service (and also rebooted the server)in my Exchange member
server and now every time I do a "browstat status", it no longer reports that
my Exchange member server is the master browser; it now correctly reports
that my DC1 is the master browser and that the 2 backup browsers for the
domain are DC1 and DC2.
A point I want to make here is that while I had the comp browser service
running and browstat status incorectly reporting that my exchange server was
the master browser, I didn't notice any problems (for instance, my DC1 and
DC2 were working fine, correctly reporting the proper results when browstat
status was ran). So, it seems to me that my exchange member server had this
problem to itself and didnt affect anything else, not even other computers
accessing resources in this exchange server. Also, this exchange member
server was responding to pings.
So, just like you said, the only thing tthat happens when the comp. browser
service is stopped is it prevents the computer from becoming a master
browser, which in my case it worked fine because my master browser is my DC1
and this Exchange member server is my VPN and we didn't want it to become a
"second" master browser because I don't think there can be 2 in the same
subnet.
And lastly,
The odd results in browstat are probably caused by the multiple
interfaces. Doesn't browstat give you separate results for each interface?
yes, it gave me 2 results, one for the physical NIC card and the other I
guess for the PPP adapter that got created as soon as the first VPN
connection was done. Here is the results:
Status for domain XXXXXX on transport
I would assume this is coming from the PPP adapter.. and if so, why does it
say that?