Re: SMS 2003 and Firewall port exceptions

"John Hiebert" <John.Hiebert@xxxxxxxxxxx> wrote in message
news:uBjVwYJuFHA.596@xxxxxxxxxxxxxxxxxxxxxxx
> I have SMS 2003 running on Windows 2003. My SQL server is a seperate
> Windows 2003 Server with SQL 2000. The SMS SQL provider is on the SQL
box.
> We have deployed the MS firewall on the SQL box. What ports need to be
open
> for the SMS management console to work? I have opened 1433 of course.
> However the SMS management console seems to be connecting on random ports.
> I think I have seen it connect on 1079, 1080, 1089, and 1103. After I
open
> these ports (what ever one its trying to use) the management console
works.
> However it seems to change ports on me. Any ideas?
>
It's possible that what you are seeing is default behavior, pls see the
following:
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932

Steve


.

Relevant Pages

  • Re: Reinstall of SMS 2003 has no Status Messages
    ... The user running SMS setup has admin rights to SQL as well correct? ... > account does not have Administrator's privileges on the SQL Server. ...
    (microsoft.public.sms.setup)
  • Re: Moving SMS SQL Database
    ... We have a customer running SMS 2003 in Advanced Security with a remote SMS ... SQL database. ... They need us to move the database to a different server. ... groups and permissions referencing the OLD SQL Server ...
    (microsoft.public.sms.admin)
  • Re: SMS Maintenance Tasks missing
    ... Wait about 10 minutes and run ACLRESET (on both the SMS and SQL server). ... >>> installed SMS 2.0 with sp1 first which included the maintenance tasks? ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 & Remote SQL2000
    ... Be 100% positive, Kim, 'cause you're right. ... Check out the SMS Technical FAQ: ... but IIRC sms does not support named instances for sql. ... >>>> correct SQL server name." ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 SP2 and SQL 2000
    ... most likely the issues is related to that you are using "core" SQL functionality to dump the database to the same file every time it back's up the SMS db. ... As Garth did mention you should disable all this SQL Server Agent jobs and rather rely on the SMS_SITE_BACKUP task instead, as it will backup all required components at the same point in time. ...
    (microsoft.public.sms.admin)
Loading