RE: port 4125
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Fri, 12 May 2006 10:58:55 GMT
Hi Carl,
Thanks for using the SBS newsgroup.
From your description, I understand the issue to be: the port 4125 is usedby other process not the RWW site. If I am off base, please don?t hesitate
to let me know.
I appreciate your time to perform pre-trouble shooting to isolate the
issue. Since it is the WWW publishing service is listening on port 4125, we
can isolate that it is some web site is listening port 4125. We can check
as follows:
1. Open IIS console, navigate to Web Sites node, right click web site
(Default Web site, Microsoft Sharepoint Administration, Sharepoint Central
Administration, companyweb and all web sites that you created) to open its
Properties page.
2. Under Web Site tab, please verify there is any web site listening TCP
4125 port. If yes, please change it listening on other port.
By default, the following web sites should be listened the ports as follows:
--Default Web Site 's port is: TCP:80, SSL port is: 443;
--SharePoint Central Administration site's port is: TCP: 8081;
-- Microsoft SharePoint Administration's port is: TCP: 4751;
-- companyweb 's port is: TCP:80, SSL port is: 444;
After you verifying the settings, please run command "iisreset" to restart
the IIS service to take effects changes.
Then please test to see if the issue fixed.
If the issue persists, please help me collect some information for analyze:
1. What is the error exact error message you received when you try to
connect to the client computer in RWW site? Please help me collet a screen
shot of the error message.
2. Have you installed ISA server on the SBS server box? What is the version?
3. Please use the PortQuery utility to find out the details about which
process is occupying port 4125 and let me know the detail information. You
can go to the following link to get the tool.
http://www.microsoft.com/downloads/details.aspx?FamilyID=8355e537-1ea6-4569-
aabb-f248f4bd91d0&DisplayLang=en
I appreciate your time. I am happy to be of assistance to you and look
forward to your reply.
Have a nice day!
Sincerely,
Jenny Wu
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: "Carl" <carlh@xxxxxxxxxx>15:28:52 GMT)
Newsgroups: microsoft.public.windows.server.sbs
Subject: port 4125
Date: 11 May 2006 08:28:46 -0700
Organization: http://groups.google.com
Lines: 11
Message-ID: <1147361326.689495.196720@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 66.227.18.31
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1147361332 17258 127.0.0.1 (11 May 2006
X-Complaints-To: groups-abuse@xxxxxxxxxx..NET CLR 1.1.4322; InfoPath.1),gzip(gfe),gzip(gfe)
NNTP-Posting-Date: Thu, 11 May 2006 15:28:52 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
Complaints-To: groups-abuse@xxxxxxxxxxTK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed00
Injection-Info: j33g2000cwa.googlegroups.com; posting-host=66.227.18.31;
posting-account=U4aD1Q0AAAAFQP9-5RdXDzBxcFbmPk-n
Path:
..sul.t-online.de!t-online.de!news.glorb.com!postnews.google.com!j33g2000cwa.
googlegroups.com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:267406
X-Tomcat-NG: microsoft.public.windows.server.sbs
According to Kb 886209, if a process other than RWW is listening on
port 4125, RWW users won't be able to connect to client desktops. We
are having this issue right now. I've went through all other strings
concerning RWW, and nothing has worked thus far.
After reading the above KB, I ran the Windows Service Process
Identifier script, and discovered that the World Wide Web Publishing
service is listening on port 4125.
Is there a way to change the port that service listens on?
.
- Follow-Ups:
- Re: port 4125
- From: Carl
- Re: port 4125
- References:
- port 4125
- From: Carl
- port 4125
- Prev by Date: Re: SBS guest on Virtual Server 2005 host?
- Next by Date: ntbackup /file contains unknown data
- Previous by thread: port 4125
- Next by thread: Re: port 4125
- Index(es):
Relevant Pages
|
Loading
