Saturday, January 13, 2007

Specified Network Name Is No Longer Available

I just came across a new one in the Exchange 2003 Exchange System Manager. In the Queue Viewer, there is the Additional Queue Information box at the bottom of the screen. This one Exchange server had a lot of messages queued up and most of the queues said: The specified network name is no longer available.

Weirdly enough, on Friday afternoon, this server was chugging along deliverying outbound mail just fine.

A little more investigation showed that DNS name resolution was working fine, too. I tried some telnet tests but the TELNET would never connect to a remote SMTP system.

Turns out that someone had blocked outbound SMTP during the evenings on the WebSense server.


At 9:06 AM, Blogger Jeff Guillet - @expta said...

I just ran into the same thing. Im my case, the Trend Interscan gateway server's SMTP service was jacked up. Tried to restart the services, but they wouldn't stop. A reboot of the gateway server fixed it.

Jeff Guillet

At 4:52 AM, Blogger Unknown said...

Thanks a lot!

At 4:53 AM, Blogger Unknown said...

Thanks a lot! You save my night)


Post a Comment

<< Home