Looking for help to resolve the following problem. Change in email addresses and host necessitated updating 4 of 5 clients on a small network last Friday. All tested out incoming & outgoing just fine. Came in Monday and all 5 client's Outlook 2003 was showing "disconnected" and displaying a uniform error message 0x8004011D, server not available. After some research and failed tests it appears that the Exchange on our Small Business Server (Windows Server 2003) disconnected the Client Systems. Question: Where on the Server do I go and fix this problem? Am guessing it is a problem with wrong/conflicting information. Have already updated the changes in User Names on the POP3 Connector Manager on the Server and this did not solve the problem. Thanks -- C Johnson
Outllok showing disconnected is most likely a network issue between your workstations and the SBS. You said you changed the Host. Do the workstations have your SBS's IP as the Primary DNS server in TCP/IP Properties of each workstation's local area connection? "C. Johnson" wrote: > Looking for help to resolve the following problem. Change in email addresses > and host necessitated updating 4 of 5 clients on a small network last Friday. > All tested out incoming & outgoing just fine. Came in Monday and all 5 > client's Outlook 2003 was showing "disconnected" and displaying a uniform > error message 0x8004011D, server not available. After some research and > failed tests it appears that the Exchange on our Small Business Server > (Windows Server 2003) disconnected the Client Systems. > Question: Where on the Server do I go and fix this problem? Am guessing it > is a problem with wrong/conflicting information. Have already updated the > changes in User Names on the POP3 Connector Manager on the Server and this > did not solve the problem. > Thanks > -- > C Johnson
No. The ipconfig or nslookup show the DNS addresses present on the router instead of the SBS. Friday, I changed the "User Name" and the incoming/outgoing server names in the Email Accounts. Everything tested okay. Monday every Outlook was disconnected from the server, but the LAN was fully functional/accessible. The TCP/IP is dynamic for each workstation. -- C Johnson "davidgold" wrote: > Outllok showing disconnected is most likely a network issue between your > workstations and the SBS. You said you changed the Host. Do the workstations > have your SBS's IP as the Primary DNS server in TCP/IP Properties of each > workstation's local area connection? > > > "C. Johnson" wrote: > > > Looking for help to resolve the following problem. Change in email addresses > > and host necessitated updating 4 of 5 clients on a small network last Friday. > > All tested out incoming & outgoing just fine. Came in Monday and all 5 > > client's Outlook 2003 was showing "disconnected" and displaying a uniform > > error message 0x8004011D, server not available. After some research and > > failed tests it appears that the Exchange on our Small Business Server > > (Windows Server 2003) disconnected the Client Systems. > > Question: Where on the Server do I go and fix this problem? Am guessing it > > is a problem with wrong/conflicting information. Have already updated the > > changes in User Names on the POP3 Connector Manager on the Server and this > > did not solve the problem. > > Thanks > > -- > > C Johnson
Sorry I should have been clearer. All of your SBS clients need to have the IP of the SBS present as the primary dns server in the TCP/IP properties of their local area connections. Say your SBS's private IP is 192.168.0.1 Then each workstations Primary DNS server must be set to same. You can either type that in manually on every PC or use some DHCP server to give it out. I doubt your router would do so, but you can use SBS's DHCP function. I usually just type it in myself. Try it on one workstation and see if it helps. "C. Johnson" wrote: > No. The ipconfig or nslookup show the DNS addresses present on the router > instead of the SBS. Friday, I changed the "User Name" and the > incoming/outgoing server names in the Email Accounts. Everything tested > okay. Monday every Outlook was disconnected from the server, but the LAN was > fully functional/accessible. The TCP/IP is dynamic for each workstation. > -- > C Johnson > > > "davidgold" wrote: > > > Outllok showing disconnected is most likely a network issue between your > > workstations and the SBS. You said you changed the Host. Do the workstations > > have your SBS's IP as the Primary DNS server in TCP/IP Properties of each > > workstation's local area connection? > > > > > > "C. Johnson" wrote: > > > > > Looking for help to resolve the following problem. Change in email addresses > > > and host necessitated updating 4 of 5 clients on a small network last Friday. > > > All tested out incoming & outgoing just fine. Came in Monday and all 5 > > > client's Outlook 2003 was showing "disconnected" and displaying a uniform > > > error message 0x8004011D, server not available. After some research and > > > failed tests it appears that the Exchange on our Small Business Server > > > (Windows Server 2003) disconnected the Client Systems. > > > Question: Where on the Server do I go and fix this problem? Am guessing it > > > is a problem with wrong/conflicting information. Have already updated the > > > changes in User Names on the POP3 Connector Manager on the Server and this > > > did not solve the problem. > > > Thanks > > > -- > > > C Johnson
Sorry,, I just realized something. If you are using exchange from your SBS and all these cllient workstations are on your LAN then you should not be setting any incoming/outgoing server either. Each Outlook client should use the Exchange Server account type. Even if you Are using the POP3 connector (which I wouldn't do either unless I had to.) "C. Johnson" wrote: > No. The ipconfig or nslookup show the DNS addresses present on the router > instead of the SBS. Friday, I changed the "User Name" and the > incoming/outgoing server names in the Email Accounts. Everything tested > okay. Monday every Outlook was disconnected from the server, but the LAN was > fully functional/accessible. The TCP/IP is dynamic for each workstation. > -- > C Johnson > > > "davidgold" wrote: > > > Outllok showing disconnected is most likely a network issue between your > > workstations and the SBS. You said you changed the Host. Do the workstations > > have your SBS's IP as the Primary DNS server in TCP/IP Properties of each > > workstation's local area connection? > > > > > > "C. Johnson" wrote: > > > > > Looking for help to resolve the following problem. Change in email addresses > > > and host necessitated updating 4 of 5 clients on a small network last Friday. > > > All tested out incoming & outgoing just fine. Came in Monday and all 5 > > > client's Outlook 2003 was showing "disconnected" and displaying a uniform > > > error message 0x8004011D, server not available. After some research and > > > failed tests it appears that the Exchange on our Small Business Server > > > (Windows Server 2003) disconnected the Client Systems. > > > Question: Where on the Server do I go and fix this problem? Am guessing it > > > is a problem with wrong/conflicting information. Have already updated the > > > changes in User Names on the POP3 Connector Manager on the Server and this > > > did not solve the problem. > > > Thanks > > > -- > > > C Johnson
C. Johnson wrote: > Looking for help to resolve the following problem. Change in email > addresses and host necessitated updating 4 of 5 clients on a small > network last Friday. All tested out incoming & outgoing just fine. > Came in Monday and all 5 client's Outlook 2003 was showing > "disconnected" and displaying a uniform error message 0x8004011D, > server not available. After some research and failed tests it > appears that the Exchange on our Small Business Server (Windows > Server 2003) disconnected the Client Systems. > Question: Where on the Server do I go and fix this problem? Am > guessing it is a problem with wrong/conflicting information. Have > already updated the changes in User Names on the POP3 Connector > Manager on the Server and this did not solve the problem. > Thanks Try posting in microsoft.public.windows.server.sbs as the POP connector is part of SBS, not Exchange, and SBS does many things its own way. What you changed on the server should have had no bearing on your clients, if I understand your post correctly - but I think you should include a lot more detail when you post in the other group.
