On Apr 13, 2010, at 8:05 AM, Grigori Solonovitch wrote: > I have an idea about a source of problem. > I have MS SQL database on the same server. > There is dedicated node name and scheduler for SQL database. > So I am running two schedulers and only one CAD service. > Everything was working fine with TSM Client 6.1.3.2, but I have upgraded this > server to 6.2.0.0 recently and started to have this problem. > I have found something strange on server. Command "netstat -a" gives: > > TCP sms-prodsrv:ms-sql-s sms-prodsrv.KUWAIT.AUB.NET:0 LISTENING > TCP sms-prodsrv:1501 sms-prodsrv.KUWAIT.AUB.NET:0 LISTENING > TCP sms-prodsrv:1501 sms-prodsrv.KUWAIT.AUB.NET:0 LISTENING > TCP sms-prodsrv:1581 sms-prodsrv.KUWAIT.AUB.NET:0 LISTENING > > As you see there are two (???????!!!!!!!!) LISTENNING for port 1501. > My minimal knowledge in TCP/IP says it is impossible. > What do you think about it?
Per page http://msdn.microsoft.com/en-us/library/ms734772.aspx and similar doc, Microsoft has its own, strange version of TCP to do port sharing. Not a fan: one should not try to fool Mother Nature. You hadn't mentioned the use of CAD before this; and attempting a mixed implementation of CAD and Scheduler is unhealthy. I'd suggest following the standard procedure defined in the client manual, "Managing multiple schedule requirements on one machine", to formulate a clean implementation, which should avoid odd problems. Richard Sims
