error '80040211' after move from win server 2000 to 2003

I have a vbscript that we moved from windows 2000 server to 2003. After the move, it started giving me this error: error '80040211' and it also gives the line number in the code where the error occurs, which is simply objEmail.Send, so I know from this, and also from my research that it's not able to send the mail because of a permissions setting somewhere.

The code was working fine before, on Windows 2000, so I don't think it's the code. I think there is just a security or permissions setting that needs to be added at the new location on 2003. We still have the old server, so I can compare the two to see if I can find a difference, but I honestly don't know where to look. I've poked around but haven't found anything in the settings that is different.
shart68Asked:
Who is Participating?
 
GovvyCommented:
You will need to look at the implementation of CDO.Message object in 2003 as the security differs from 2000 Server
0
 
RobSampsonCommented:
Is the SMTP server a third server?  If so, my feeling is that the SMTP server needs to allow the IP address of the 2003 box to relay message through it.

Regards,

Rob.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
shart68Author Commented:
Yes, the SMTP is another server, and it knows the IP address, which is the same as it was on the old machine.
0
 
shart68Author Commented:
Rob,

Could you provide some clues about the implementation of CDO.Message object in 2003. I'm having trouble finding any good documentation on it.
0
 
shart68Author Commented:
Sorry, I meant Govvy on the last question, not Rob. Anyone, actually.
0
 
shart68Author Commented:
Thanks Govvy. From the crash course I was able to figure out that we did not have SMTP installed on IIS, so we did that, and now we just need to restart, and hopefully that will fix it. Since this is a production server, we will probably wait until early morning to do the restart, so I will let you know tomorrow if that fixed it. Thanks!
0
 
GovvyCommented:
No problem
0
 
shart68Author Commented:
Installing SMTP on IIS (from the link from Govvy) as well as turning off McAfee blocking, was what fixed it. It is working now. Thanks for your help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.