Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to login to MAS server via RDP after 2-3 weeks of service 1

Status
Not open for further replies.
Jan 19, 2010
23
Hi we have a 3 MAS server vmd running 5.2 on windows 2003 sp2 with an exchange 2007 back end and we have this weird thing that causes each mas server's ability to login to windows to stop working after 2-3 weeks of service.

After a few days of the MAS service continuing to operate the server completely dies and we need to do a hard reboot to get it back up.

the current way of dealing with this is to shut down ports on the server that is about to go and then reboot it and then bring it back into service just before its windows login capability stops working.

We know it is about to go because when you log into the server and run task manager you are unable to see running processes.

There don't seem to be any error messages in event viewer.

Has anyone run into anything like this?

thanks
Goz
 
You should install the same version of tools on the MAS that the Exchange server is running. So apply Exchange 2007 SP1, for sure. Then apply Exchange 2007 rollup 10 for SP1.

 
Update...

So our provider has rebuilt the vmd with new mas servers and we continue to have the same issue.


Avaya is now saying that our set up is not supported due to the network config...

we have our main site which has our cm server and one mas server and then we have "dedicated 40 meg ethernet link" to a hosting facility where we have another Mas server and our exchange server.

Avaya is saying that having to servers in one VMD is not supported if they are in different locations is this correct?
 
That is Avaya's usual statement regarding MAS placement and their relationship to where the backend resides (Exchange in this case). Avaya will not support MAS servers that are in the same VMD but in different LANs/sites. Avaya also will not support MAS servers being remote from the backend/Exchange.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top