With CallManager 3.3, SQL 2000 is used - in all the installation notes there is no mention of NetBIOS Name Resolution. During a recent installation where we had some subscribers in different IP networks than the publisher we had some odd problems that appeared then disappeared and I am not sure whether it was a Name Resolution problem or not.
We definately had a DNS issue but this was sorted quickly, after this we saw some odd issues that looked like database inconsistencies between the Publisher and one of the subscribers but we had no errors logged. What I failed to find through looking on MS's and Cisco's website was whether SQL 2000 uses any NetBIOS/RPC calls and therefore relies on NetBIOS Name Resolution.
I would be grateful if anyone who has experienced any odd issues and resolved them would reply and offer some insight into SQL 2000 and its underpinnings.....
Andy
We definately had a DNS issue but this was sorted quickly, after this we saw some odd issues that looked like database inconsistencies between the Publisher and one of the subscribers but we had no errors logged. What I failed to find through looking on MS's and Cisco's website was whether SQL 2000 uses any NetBIOS/RPC calls and therefore relies on NetBIOS Name Resolution.
I would be grateful if anyone who has experienced any odd issues and resolved them would reply and offer some insight into SQL 2000 and its underpinnings.....
Andy