Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Windows Server 2003 Service Pack 1 |
|---|---|
| Date: | Tue, 19 Apr 2005 11:08:39 +0200 |
Hi all, We are preparing for the upgrade to SP1 as well on our DCs and Exchange servers. The following information I found on the internet Problem with Dell and HP Bios Dell and HP servers require a BIOS upgrade before you can install SP1. So, I was wrong when I thought that there should be no problem on mainstream servers. Perhaps you see what I mean about each service pack having its own personality. Problem with Exchange 2003 Does your Windows Server 2003 run Exchange 2003? If so, Windows Hosting recommend waiting for Exchange 2003 Server SP2, before applying Windows Server 2003 SP1. As far as Microsoft themselves are concerned, there is but one issue with SP1 and Exchange 2003, namely that OWA won't work properly on a clustered Exchange 2003 server. Can someone confirm this ? Or have problems expirienced with these issue's ? Best regards, Ronald Balk Intrum Justitia - GROUP-IT -----Original Message----- From: Bones [mailto:the.bones@gmail.com] Sent: Monday, April 18, 2005 7:48 PM To: focus-ms@securityfocus.com Subject: Re: Windows Server 2003 Service Pack 1 We upgraded this weekend and only found one (security related) anomaly so far. If you are familiar with Exchange Server 2003, we had several "virtual SMTP servers" setup on various ports for the various domains we manage. Inbound e-mail is configured to be accepted in TCP25, but we have other SSL wrapped SMTP connections on higher ports that our external employees use to drop off mail back to the organization securely. Example: mail.domain1.com running on TCP 25 (general inbound mail connection) mail.domain1.com running on TCP 2525 (SSL/TLS mail for domain1 clients) mail.domain2.com running on TCP 2526 (SSL/TLS mail for domain2 clients) mail.domain3.com running on TCP 2527 (SSL/TLS mail for domain3 clients) etc. Anyway, the high-port virtual SMTP servers no longer work. We have to have all users change their mail client config to route them through the general Internet inbound connection on TCP25 (which cannot be wrapped in SSL for obvious reasons). So far M$ has no explanation. ;-/ It's a minor exposure, but not one we would like to have. Bones ------------------------------------------------------------------------ --- ------------------------------------------------------------------------ --- --------------------------------------------------------------------------- ---------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Re: using certificates in Outlook for encryption, Zack Schiel |
|---|---|
| Next by Date: | SecurityFocus Microsoft Newsletter #237, Marc Fossi |
| Previous by Thread: | Re: Windows Server 2003 Service Pack 1, Bones |
| Next by Thread: | Integrating Domain and VPN Login, Ryan Kubiak |
| Indexes: | [Date] [Thread] [Top] [All Lists] |