Re: Exchange Outgoing E-Mail
- From: v-natliu@xxxxxxxxxxxxxxxxxxxx ("Nathan Liu [MSFT]")
- Date: Thu, 15 Sep 2005 09:25:27 GMT
Hi Kiran,
Thank you for your email.
1. I checked the Ports.txt file, and found the following information:
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 2512
Please check PID 2512 in task manger to identify the process listening on
80. To do so, open the Task Manager, click Processes tab, click View ->
Select Columns -> PID (Process Identifier) -> OK.
2. I checked the IIS screen shot picture, and found the following
information:
1) Default Web Site is listening on Port 3200, SSL Port 444.
2) Companyweb is listening on Port 80, SSL Port 443.
However, by default, the Default Web Site listens on Port 80, SSL Port 443,
the Companyweb listens on Port 80, SSL Port 444, the Microsoft SharePoint
Administration listens Port 4588, the SharePoint Central Administration
listens Port 8081. Since many items were changed, I suggest you click the
following link to install the Metabase Explorer tool on the SBS Server, run
MBExplorer (Metabase Explorer), click Metabase -> Import key, locate the
attachment W3SVC.mbk file and then import it, then you can compare these
settings.
The IIS 6.0 Resource Kit Tools
http://support.microsoft.com/default.aspx?scid=kb;en-us;840671#8
3. Based on my research, these messages "System.ArgumentNullException: No
message was deserialized prior to calling the DispatchChannelSink.
Parameter name: requestMsg at ..." are most likely related to the .NET
Framework 1.1, please refer to the following link to install the Microsoft
NET Framework 1.1 Service Pack 1 for Windows Server 2003:
Microsoft .NET Framework 1.1 Service Pack 1 for Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?familyid=AE7EDEF7-2CB7-4864-
8623-A1038563DF23&displaylang=en
I appreciate your time and cooperation. If anything is unclear, please feel
free to let me know. I am looking forward to hearing from you.
Best regards,
Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Kiran" <kiran.vithal@xxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>Subject: Re: Exchange Outgoing E-Mail
>Date: 29 Jul 2005 04:06:43 -0700
>Organization: http://groups.google.com
>Lines: 14
>Message-ID: <1122635203.925477.177300@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <1122318005.396389.230980@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> <1122557001.324076.3430@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> <sRazR69kFHA.588@xxxxxxxxxxxxxxxxxxxxx>
>NNTP-Posting-Host: 62.255.32.14
>Mime-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1122635209 5671 127.0.0.1 (29 Jul 2005
11:06:49 GMT)
>X-Complaints-To: groups-abuse@xxxxxxxxxx
>NNTP-Posting-Date: Fri, 29 Jul 2005 11:06:49 +0000 (UTC)
>In-Reply-To: <sRazR69kFHA.588@xxxxxxxxxxxxxxxxxxxxx>
>User-Agent: G2/0.2
>Complaints-To: groups-abuse@xxxxxxxxxx
>Injection-Info: o13g2000cwo.googlegroups.com; posting-host=62.255.32.14;
> posting-account=Crt7Lg0AAACbv9BNacSzZMkykbR_YiJH
>Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews.google.com!o1
3g2000cwo.googlegroups.com!not-for-mail
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:139829
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi Nathan
>
>Thank you for your very informative message. Having looked at the SMTP
>issue, I am concerned that when my server is down for whatever reason,
>that mail will not be delivered.
>
>The question is that if the server is down is there a way of sending to
>my pop address at my isp, and then when the server is back it, it will
>download automatically from there?
>
>Many thanks
>
>Kiran
>
>
.
- Prev by Date: RE: SBS 2003 Firewall Failure
- Next by Date: Re: Folders and permisisons
- Previous by thread: Re: Exchange Outgoing E-Mail
- Next by thread: Re: Exchange Outgoing E-Mail
- Index(es):
Relevant Pages
|
