Dillie-O's questions

We have a few websites that we are running on one instance of IIS that need to be mapped for each of their domain names. For example.

Site A has the domain name coolness.com
Site B has the domain name 6to8Weeks.com
Site C has the domain name PhatTech.com

When I look at the "Web Site Identification" section of the IIS configuration window, I notice that I can specify an IP address and port, but if I click the Advanced button, I can also configure the site based on host header values as well.

How do I configure each site in IIS? Ideally I would like them to all be able to listen to port 80, so I don't have weird URLs, but I'm not sure if I do this using headers, IP addresses, both, or something else.

I'm using the database publishing wizard to synchronize my local SQL Server 2005 database with my GoDaddy hosting account. I've followed all their directions and haven't had an issue for several months now.

Recently when I attempt to connect and synchronize, I get the following error:

TITLE: Test failed
------------------------------
The underlying connection was closed: Could not establish trust relationship
for the SSL/TLS secure channel. (System.Web.Services)
------------------------------
ADDITIONAL INFORMATION:
The remote certificate is invalid according to the validation procedure.
(System)
------------------------------

GoDaddy has verified that they can connect to the database through the wizard using a machine that is not connected to their internal network.

I'm in the process of trying things from a different machine, but I've noticed lately that both IE and Firefox are having problems connecting to accounts that require SSL certificates, such as Google Analytics.

Is there something I'm missing that could be mucking up SSL connections in general on my machine?

I asked this over on SO with little success. I was wondering if any SF folks had some insight...

I have a SSIS 2005 package that is up and running in our production environment. The package uses an SMTP Connection Manager to send an e-mail message out to a designated user. We have a scheduled job that executes this package, and also overrides the SMTP connection string so that the package can target the test or production mail server, which makes it possible to keep a single service on both our test and production servers, just configured differently.

We recently changed the server name of our production mail server and went into the scheduled job and changed the command prompt values that run to point to the new server. However, the next morning the job failed and the error log indicated that the job tried to connect to the old mail server.

Is there something I'm missing to updating the SSIS package parameters? Do I have to delete the existing package, and then reimport and reschedule the job again in order for the new server change to hold?

Note: Domains and IPs obfuscated for security.

We have an internal web application that sends e-mail reports out to various vendors. Our primary exchange server (domain name co.XXX.YY.ZZ) does not relay mail, so one of our web servers (Windows Server 2003) is setup with the basic SMTP server to do mail relaying (domain name ABABA.net).

We have about 300 vendors on file and the application works fine. However, one vendor has reported not getting the e-mails sent to them. We've verified the e-mail goes out through our own server logs:

12.34.567.8, ntintwebp, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, 12.34.567.8, 0, 36, 49, 250, 0, MAIL, -,  FROM:<[email protected]>,
12.34.567.8, ntintwebp, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, 12.34.567.8, 0, 25, 28, 250, 0, RCPT, -,  TO:<[email protected]>,
12.34.567.8, ntintwebp, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, 12.34.567.8, 0, 81154, 132, 250, 0, DATA, -, <[email protected]>,
98.765.432.100, OutboundConnectionResponse, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 47, 0, 114, 0, 0, -, -, 220 mail.schmoe.org Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at  Mon, 29 Dec 2008 09:47:41 -0700 ,
98.765.432.100, OutboundConnectionCommand, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 47, 0, 4, 0, 0, EHLO, -, ntintwebp.ABABA.net,
98.765.432.100, OutboundConnectionResponse, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 109, 0, 40, 0, 0, -, -, 250-mail.schmoe.org Hello [11.222.333.44],
98.765.432.100, OutboundConnectionCommand, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 109, 0, 4, 0, 0, MAIL, -, FROM:<[email protected]>,
98.765.432.100, OutboundConnectionResponse, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 140, 0, 47, 0, 0, -, -, 250 2.1.0 [email protected] OK,
98.765.432.100, OutboundConnectionCommand, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 140, 0, 4, 0, 0, RCPT, -, TO:<[email protected]>,
98.765.432.100, OutboundConnectionResponse, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 187, 0, 26, 0, 0, -, -, 250 2.1.5 [email protected] ,
98.765.432.100, OutboundConnectionCommand, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 187, 0, 4, 0, 0, BDAT, -, 81476 LAST,
98.765.432.100, OutboundConnectionResponse, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 718, 0, 85, 0, 0, -, -, 250 2.6.0  <[email protected]> Queued mail for delivery,
98.765.432.100, OutboundConnectionCommand, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 718, 0, 4, 0, 0, QUIT, -, -,
98.765.432.100, OutboundConnectionResponse, 4/23/2009, 9:47:02, SMTPSVC1, NTINTWEBP, -, 750, 0, 61, 0, 0, -, -, 221 2.0.0 mail.schmoe.org Service closing transmission channel,

The IT department for the vendor did some research on their end and indicated that the ABABA.net DNS records were not valid and that the [email protected] address was an invalid e-mail address (even through the FROM field is using our valid [email protected] address. In addition they said that the [email protected] address fails the syntax, DNS, and SMTP checks.

We've had a couple of other vendors reporting issues, but having them white list the yavco.net domain has resolved those issues, since I believe they were spam related, and not delivery related.

Any ideas on how to resolve this server issue?

IIS/Web Applications has been a tricky issue in the shops I've worked in over time.

On one hand, IIS is a service built into the server (by in large) and is typically the responsibility of the server administrators to maintain and configure. When an issue comes up, they know what needs to happen, or can at least diagnose to the point where they say, "Something is wrong with the web app" and have the developer debug their code.

However, each web application on the server is unique and has a lot of nuances that gets can be complex based on the issues at hand.

On the other hand, each web application is unique in many ways and had specific issues that need to be dealt with and the developer is the person that knows the most about the application. If the web.config file needs to be modified for debugging, or an IIS starts giving grief to the web application, the developer should know where the issue lies and fix it accordingly, either due to IIS or the application itself.

However, allowing a developer to go in and tweak with IIS on their own becomes a serious issue because some settings/optimizations can seriously muck up with the server performance and stability.

So where does the balance lie? Should the server admins be IIS gurus and handle all of those issues and I simply send the site files over deployment, or should the developer assume responsibility for the server and IIS issues and deal with them accordingly?