?
Solved

Prevent DNS Server service from utilizing port 4125, which breaks SBS2003 RWW

Posted on 2007-04-05
5
Medium Priority
?
1,559 Views
Last Modified: 2010-04-01
I have a customer's Small Business Server which sometimes Remote Web Workplace stops working.

Using http://support.microsoft.com/kb/886209, and the command [ netstat -aon | find ":4125" ], I found that DNS.exe is utilizing port 4125.  Restarting the DNS Server service temporarily fixes the problem, but it may come back in a month or so.  (last few months the problem was fixed by rebooting the server until I dug a little deeper to pinpoint the problem)

The MS KB article explains how to stop the RPC service from not using that port... does anyone know of a way to stop DNS server from using that port also?
0
Comment
Question by:JacksonTechnical
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 16

Expert Comment

by:AdamRobinson
ID: 18859491
If I'm not mistaken shouldn't your DNS server be using port 53?  

Have you tried re-configuring the DNS Server?
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 18861793
DNS was using 4125?  Are you sure?  What made you think that?  

At any rate, you would still follow the steps outlined in the KB article to stop RPC from using port 4125 because even if it was DNS.exe, that service would not access the port directly, it'd use RPC.

Jeff
TechSoEasy
0
 

Author Comment

by:JacksonTechnical
ID: 18862024
DNS was not configured to listen on any alternate ports.  I think it could have been an outgoing port connection to itself.  My netstat pipe find command prompt got closed or I would have posted the output.

To your question, "What made me think that" was the output from the netstat command and the PID matching the DNS service in task manager's process list.

We manage over 80 SBS servers, first time I've seen this.  But apparently it can happen... I'll go ahead and apply the RPC registry entries and hope for the best.

Also, FYI, for everyone else out there... SBS's RWW and it's port 4125 redirecting to 3389 on the end client machines does not listen like a normal port listening service.  It does not respond to a telnet prompt (no blank screen or anything), and it does not show up when you issue a NETSTAT command... but it is listening and does work when you forward your WAN traffic to it.  Just shows that a process can listen on a port and not register with normal tools to determine what is listening on what port.

0
 
LVL 74

Accepted Solution

by:
Jeffrey Kane - TechSoEasy earned 1500 total points
ID: 18874660
That's true that 4125 wouldn't respond to a telnet request.  That's one of the security features of Small Business Server.  4125 will ONLY respond to the ActiveX encrypted request it receives while you are already connected via port 443.  It is otherwise not listening.

Jeff
TechSoEasy
0

Featured Post

Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Suggested Courses

801 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question