bbwin on windows server 2008 - no data sent to bbdisplay 🔗 link

 Hi all,

I try to set up bbwin on windows 2008.
the only network packets I get from the bbwin server are like this one :
1.2.3.4    224.0.0.252    LLMNR    Standard query A yourfirstbbdisplay

my bbwin.cfg works fine on windows 2003, but 2008 doesn't seem to work
fine.

did anyone already experience this ?

Hi

I am running it successfully on a Windows 2008 server no problems. I
assume you opened the 1984 port on the machine as you can see the
network packets. Have you checked the event log for BBWin related
errors? 

-----Original Message-----
From: pkc_mls [mailto:user-06f34394900f@xymon.invalid] 
Sent: 28 July 2010 09:32 AM
To: xymon at xymon.com
Subject: Re: [xymon] bbwin on windows server 2008 - no data sent to bbdisplay

Le 7/27/2010 4:57 PM, Neil Franken a écrit :

Hi 

Hi

I am running it successfully on a Windows 2008 server no problems. I
assume you opened the 1984 port on the machine as you can see the
network packets. Have you checked the event log for BBWin related
errors? 

I can't see any packet sent to my bbdisplay, and there is no
yourfirstdisplay server defined.
I'll try to add this to the hosts file, but that's not a correct solution.

event log doesn't show any error.
how can I get more traces in the bbwin.log ?
I tried to set the log level to 9, without success.

Regards
Neil

-----Original Message-----
From: pkc_mls [mailto:user-06f34394900f@xymon.invalid] 
Sent: 28 July 2010 09:32 AM
To: xymon at xymon.com
Subject: Re: [xymon] bbwin on windows server 2008 - no data sent to bbdisplay

Le 7/27/2010 4:57 PM, Neil Franken a écrit :

Hi 

Hi

I am running it successfully on a Windows 2008 server no problems. I
assume you opened the 1984 port on the machine as you can see the
network packets. Have you checked the event log for BBWin related
errors? 

I can't see any packet sent to my bbdisplay, and there is no
yourfirstdisplay server defined.
I'll try to add this to the hosts file, but that's not a correct solution.

event log doesn't show any error.
how can I get more traces in the bbwin.log ?
I tried to set the log level to 9, without success.

Regards
Neil

wrote:

Are you a 100% sure that there is a not a firewall blocking the network
transmission?


-----Original Message-----
From: pkc_mls [mailto:user-06f34394900f@xymon.invalid]

Sent: 28 July 2010 09:32 AM
To: xymon at xymon.com

Subject: Re: [xymon] bbwin on windows server 2008 - no data sent to
bbdisplay

Le 7/27/2010 4:57 PM,...

Le 7/28/2010 9:33 AM, Neil Franken a écrit :

For BBWin to log very verbosely add the following to the BBWin.cfg file.

<setting name="loglevel" value="4" />

I use that to track down problems

-----Original Message-----
From: pkc_mls [mailto:user-06f34394900f@xymon.invalid]
Sent: Wednesday, July 28, 2010 3:32 AM
To: xymon at xymon.com
Subject: Re: [xymon] bbwin on windows server 2008 - no data sent to bbdisplay

Le 7/27/2010 4:57 PM, Neil Franken a écrit :

Hi

Hi

I am running it successfully on a Windows 2008 server no problems. I
assume you opened the 1984 port on the machine as you can see the
network packets. Have you checked the event log for BBWin related
errors?

I can't see any packet sent to my bbdisplay, and there is no yourfirstdisplay server defined.
I'll try to add this to the hosts file, but that's not a correct solution.

event log doesn't show any error.
how can I get more traces in the bbwin.log ?
I tried to set the log level to 9, without success.

Regards
Neil

Le 7/28/2010 6:50 PM, Storer, Raymond a écrit :

Can you please post your BBWin.cfg file (obfuscating any IPs etc, of course)? If the firewall is not the problem it sounds like the server is not correctly defined in the BBWin.cfg file. Please note, if you have not disabled the UAC (which I strongly recommend you DO NOT) you will need to either change the permissions on the BBWin.cfg file so you can edit and save it or start notepad.exe as an Administrator in order to successfully save your changes.

Ray

-----Original Message-----
From: pkc_mls [mailto:user-06f34394900f@xymon.invalid]
Sent: Thursday, July 29, 2010 3:29 AM
To: xymon at xymon.com
Subject: Re: [xymon] bbwin on windows server 2008 - no data sent to bbdisplay

Le 7/28/2010 6:50 PM, Storer, Raymond a écrit :

Can you please post your BBWin.cfg file (obfuscating any IPs etc, of course)? If the firewall is not the problem it sounds like the server is not correctly defined in the BBWin.cfg file. Please note, if you have not disabled the UAC (which I strongly recommend you DO NOT) you will need to either change the permissions on the BBWin.cfg file so you can edit and save it or start notepad.exe as an Administrator in order to successfully save your changes.

here it is

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<bbwin>
        <setting name="bbdisplay" value="x.x.x.x:1984" />
        <setting name="bbdisplay" value="x.x.x.x:1984" />
        <!-- BB Pager Part -->
        <!-- <setting name="usepager" value="false" /> -->
        <!-- <setting name="bbpager" value="yourfirstbbpager" /> -->
        <!-- <setting name="bbpager" value="yourfirstbbpager" /> -->
        <!-- <setting name="pagerlevels" value="red yellow" /> -->

        <!-- proxy connection settings -->
        <!--    <setting name="useproxy" value="false" /> -->
        <!-- <setting name="proxy" value="[user:password@]host[:port]"/> -->

        <!-- bbwin mode local or central -->
        <setting name="mode" value="local" />
        <setting name="configclass" value="win32" />

        <setting name="autoreload" value="true" />
        <setting name="timer" value="5m" />
        <load name="cpu" value="cpu.dll"/>
        <load name="disk" value="disk.dll"/>
        <load name="externals" value="externals.dll"/>
        <load name="filesystem" value="filesystem.dll"/>
        <load name="memory" value="memory.dll"/>
        <load name="msgs" value="msgs.dll"/>
        <load name="procs" value="procs.dll"/>
        <load name="stats" value="stats.dll"/>
        <load name="svcs" value="svcs.dll"/>
        <load name="uptime" value="uptime.dll"/>
        <load name="who" value="who.dll"/>
        <setting name="loglevel" value="4" />
        <setting name="logpath" value="C:\Program Files\BBWin\logs\BBWin.log"/>
        <!--  If true, the agent will report reporting failures as warning events -->
        <setting name="logreportfailure" value="true" /> </bbwin> <cpu>
        <!-- If true, the agent  will always report with green status -->
        <setting name="alwaysgreen" value="false" />
        <setting name="default" warnlevel="90" paniclevel="95" delay="3" /> </cpu> <disk>
        <!-- If true, the agent  will always report with green status -->
        <setting name="alwaysgreen" value="false" />
        <!-- Level can be given by % or size unit mb, gb, tb -->
        <setting name="default" warnlevel="85%" paniclevel="95%" />
        <!-- custom rules examples
        <setting name="C" warnlevel="70%" paniclevel="400mb" />
        <setting name="E" ignore="true" /> -->
        <!-- If true, the agent will check remote drives -->
        <setting name="remote" value="false" />
        <!-- If true, the agent will check that cd/dvdrom drives are empty -->
        <setting name="cdrom" value="false" /> </disk> <externals>
        <setting name="timer" value="3m" />
        <setting name="logstimer" value="60s" />
        <!-- externals launch examples
        <load value="cscript mybbscript.vbs" />
        <load value="myexternal.exe" />
        <load value="cscript wlbs.vbs" timer="15m" />
        <load value="cluster.exe" timer="90s" /> --> </externals> <memory>
        <!-- If true, the agent  will always report with green status -->
        <setting name="alwaysgreen" value="false" />
        <setting name="physical" warnlevel="78" paniclevel="98" />
        <setting name="page" warnlevel="70" paniclevel="90" />
        <setting name="virtual" warnlevel="78" paniclevel="90" /> </memory> <msgs>
        <setting name="alwaysgreen" value="false" />
        <setting name="delay" value="1h" />
        <match logfile="System" type="error" alarmcolor="red" />
        <match logfile="System" type="warning" alarmcolor="yellow" />
        <match logfile="Application" type="error" alarmcolor="red" />
        <match logfile="Application" type="warning" alarmcolor="yellow" />
        <match logfile="Security" type="fail" />

        <!-- Some ignore rules examples -->
        <!-- <ignore logfile="Application" eventid="1030" /> -->
        <!-- <ignore logfile="System" source="W32Time" /> --> </msgs> <procs>
        <!-- some procs rules example -->
        <!-- <setting name="drwtsn" rule="-1" alarmcolor="red" /> -->
        <!-- <setting name="pageant.exe" rule="=1" comment="Putty agent deamon"
/> -->
</procs>
<svcs>
        <!-- If true, the agent  will always report with green status -->
        <setting name="alwaysgreen" value="false" />
        <!-- If true, the agent will restart all "automatic  services" which would be stopped -->
        <setting name="autoreset" value="false" />
        <setting name="alarmcolor" value="yellow" />
        <!-- The line bellow show you svcs rules. If the "Automatic Updates"
service is stopped,  it will be automatically restarted and a red status will be sent -->
        <!-- until the service get it's correct status  -->
        <setting name="Automatic Updates" value="started" autoreset="true"
alarmcolor="red" />  -->
</svcs>
<uptime>
        <setting name="delay" value="30m" />
        <setting name="maxdelay" value="365d" /> </uptime> </configuration>

Ray

CONFIDENTIALITY NOTICE:  This email and any attachments are for the
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.

Le 7/29/2010 2:50 PM, Storer, Raymond a écrit :

Back to the firewall... have you tried disabling the firewall service, rebooting, and then seeing if you see any reports from this machine? You can try simply stopping the firewall service if you like, but I've seen the network stack get pretty stupid after just stopping it--so, I recommend a disable and a reboot.