"dimbrogno2010" <> wrote in message
news:...
>
> I have a 300 user network running 1 w2003 servers with 450 clients and
> about 150 email accounts. The server I run my email service on (not an
> Exchange server, just a regular Server 2003 server running Imail by
> Ipswitch) has been having problems. For about a week now, users have
> been getting an error when trying to send email that states "Bad Socket
> Error". I have run several virus and malware scanners that come back
> clean on all my servers. I need help finding the solution to this
> problem since I don't know much about socket problems.
>
> When I ran the TCPVIEW program, it sends back information like this:
> dfssvc.exe:1436 UDP server:1096 *:*
> dns.exe:1500 TCP server:2002 localhost:ldap ESTABLISHED
> dns.exe:1500 TCP server:1030 server:0 LISTENING
> dns.exe:1500 TCP server:domain server:0 LISTENING
> dns.exe:1500 UDP server:62982 *:*
> dns.exe:1500 UDP server:54244 *:*
> dns.exe:1500 UDP server:51931 *:*
> dns.exe:1500 UDP server:60669 *:*
> dns.exe:1500 UDP server:57585 *:*
> dns.exe:1500 UDP server:50646 *:*
> dns.exe:1500 UDP server:60155 *:*
> dns.exe:1500 UDP server:53987 *:*
> dns.exe:1500 UDP server:53472 *:*
> dns.exe:1500 UDP server:64780 *:*
> dns.exe:1500 UDP server:49360 *:*
> dns.exe:1500 UDP server:56813 *:*
> dns.exe:1500 UDP server:61182 *:*
> dns.exe:1500 UDP server:52701 *:*
> dns.exe:1500 UDP server:50645 *:*
> dns.exe:1500 UDP server:64008 *:*
> dns.exe:1500 UDP server:57840 *:*
> dns.exe:1500 UDP server:62209 *:*
> dns.exe:1500 UDP server:53471 *:*
> dns.exe:1500 UDP server:55527 *:*
>
> The dns.exe entries go on nearly forever if I sent the entire log. If
> I restart the server the problem is fixed for a while and then recurs.
> Any help would be deeply appreciated. Thanks!
>
>
> --
> dimbrogno2010
Are you saying the socket error is being reported on the Windows 2003
server, or at the client side?
I was trying to look up the error, but the "Bad Socket Error" you provided
is too general, and I was getting too many varied hits. Can you post the
actual error verbatim, including any event log EventID#s and their source
names, please? This will help us search and lookup the specific error you
are getting.
What you are seeing regarding DNS service ports is normal after installing
the DNS vulnerability hotfix patch. The hotfix reserves ports for the
service location specific response ports to reduce the possibility of DNS
query hijacks and cache poisoning. Read teh followign for more specifics:
The DNS Cache Poisoning Vulnerability, Microsoft KB953230 Patch, and Ports
Reservation Explained
http://msmvps.com/blogs/acefekay/arc...explained.aspx
As far as the TCP socket errors, I do not believe this is your cause,
especially since this hotfix came out in July, 2008. So if it was installed
over a year ago and things were running fine until recently, I believe the
cause is elsewhere. However, there's always a chance that the End Point
Mapper is running out of ports for teh application (the mail system you have
installed), so there are no more ports to map connections. It is possible
that the mail app or some other network based app on the server, isn't
releasing ports when it's done with them. My article above explains some of
that. It could also be an antivirus app that is causing it.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Similar Threads
Linear Mode
