TMS-Low Battery on Remote Control

[Conquest_Tsi]

Hi Guys,

Just a question on this feature of TMS. All other system logs come up ok but with the low battery on remote control all the check boxes are greyed out. Do i need to do anything further to enable this functionality?

[DRI]

What version of TMS?

Is there any event in the Event Count? If there all 0, then no events with regards to low battery on remote control have been trapped by the TMS, i.e. SNMP Trap event. Therefore, nothing to look at.

If knowing when your remotes have a low batteries is important to you, then I'd suggest setting up a Event Notification to be sent to a particular user account or the TMS Administrator when this occurs, i.e. see Systems>Event Notification.

rgds,

DRI

[Conquest_Tsi]

version 11.6

No there is no event counts at all!

Just thought it was weird that none have come up.

Thanks for that buddy, didnt know that even notification was even there!

Do i need to have exchange integration for it to email me?

[DRI]

Do i need to have exchange integration for it to email me?

No, you don't need exchange integration for this, TMS simply sends to the user's email address specified in the user's details in TMS

[Conquest_Tsi]

Hey Buddy,

Having some issues with this, had our email guy check relaying from the TMS box to a valid email address and worked fine. can ping/communicate with the email server fine from the TMS box.

However when i try putting in the mail servers IP, TMS rejects this 'Mail Settings not saved: Communication with the SMTP server failed', any help?

[robertk]

Hey Buddy,

Having some issues with this, had our email guy check relaying from the TMS box to a valid email address and worked fine. can ping/communicate with the email server fine from the TMS box.

However when i try putting in the mail servers IP, TMS rejects this 'Mail Settings not saved: Communication with the SMTP server failed', any help?

If you add your email address to

Administrative Tools -> Network Settings -> Event Notification: E.mail Addresses to Receive System and Network Notifications: ...

Then TMS will try to send YOU an test-email when you save the MAIL SETTINGS.

This might help you find the problem.

//Robert

[Conquest_Tsi]

If you add your email address to

Administrative Tools -> Network Settings -> Event Notification: E.mail Addresses to Receive System and Network Notifications: ...

Then TMS will try to send YOU an test-email when you save the MAIL SETTINGS.

This might help you find the problem.

//Robert

Hi Robert,
Didnt know that field existed, but still a no-go.
Anyone else have any tips/help?
Very strange.

[DRI]

Have you tried DNS name?

Anti-Virus or another Anti-SW is the most common culprit by blocking programs access to port 25 outgoing.

I'd also take a look in log-web.txt or log-scheduler.txt for errors around sending mail, i.e. C:\Program Files\Tandberg\TMS\wwwtms\data\logs\tmsdebug.

You could also try sending a test message to the address you are trying to send to manually via telnet and make sure you are not being rejected for relaying, authentication, etc. But,is this what your email guy did?

As a last resort, then I'd run an ethereal trace between the TMS and SMTP server from the TMS to see exactly what is happening when you try to to save the mail settings.

[Conquest_Tsi]

Yes tried DNS name etc
No antivirus/firewall.
Our Server admin did the manual testing and all worked as it should.

Did the packet sniffing and all is communicating fine between the hosts!

Have attached log-web.txt error log for reference, seems to be an inconsistency in there somewhere.

It is an Appliance and ALOT of the windows services have been disabled, any particular ones need to be enabled for this service to work?

[DRI]

Yes tried DNS name etc
No antivirus/firewall.
Our Server admin did the manual testing and all worked as it should.

Did the packet sniffing and all is communicating fine between the hosts!

Have attached log-web.txt error log for reference, seems to be an inconsistency in there somewhere.

It is an Appliance and ALOT of the windows services have been disabled, any particular ones need to be enabled for this service to work?

No to your question...and I can see the timeouts in the log web...but what is the ip address of the TMS server? Is it possible there is some kind of NATing going on here or is the customer using both an internal and external mail server? You say you packet sniffed and all is communicating fine between the TMS and SMTP server but it's obvious from the log web that there is a timeout occuring after the helo is sent so I'm surprised you didn't see more in the sniff. But did you sniff from both the TMS and SMTP server or just TMS?

[Conquest_Tsi]

tms is 10.138.42.20, no NAT whatsoever, all inside LAN, VC infrastructure on a VLAN, server on another-communication is open between the VLANS.

Im kinda leaning to toward a higher layer problem, like TMS software issue, its running 11.6.

Just sniffed from the TMS server, but will try again from both and record the logs.

[Conquest_Tsi]

Hi Guys,

Sorry for the late reply but FYI

TB couldnt figure out why the mail settings page wouldnt apply correct settings. This was on the appliance version and then also when that database was migrated to a dedicated server.

However settings would apply fine if they were entered in during an uprade, and also if you delve into the database and update it manually. Now works fine :0