RE: Server 2003 DNS issue - Fixed
I got this working but not exactly sure what made it start working. Called Qwest and they tested the lines and said things were working fine from their perspective. I figured that. Had the office reboot the DSL modem. They did this while I was connected since I lost connectivity. Logged back in and same error messages. While working remotely deleted DNS from the box, rebooted and reinstalled DNS. Ran SBS Connect to Internet wizard. Same problem. Checked everything again with other working SBS boxes and all settings were correct. Frustrated quit and went out and worked on my car. Saturday morning went to the office with my laptop. Checked everything locally just in case being remote was an issue. Same error messages. Configured laptop with server wan settings, connected to the DSL modem and same error messages. What! Must be a Qwest issue somewhere. Called Qwest support and tried to explain what was happening and what I had determined to the woman. Went through the basic support steps and she said it was a server issue. Uh no it wasn't could you check with someone else. On hold for a while, line got disconnected, waited five minutes with no call back and called in again. Got a different tech this time but he actually knew what I was talking about. Went through the basic support steps again with the same result. Put on hold while he went to check on some things and talk with another tech. Things didn't make sense so we started from the beginning again with the basic support steps. After rebooting the DSL modem, open command prompt, ping by IP working. Ping by name working. OK what changed. Open IE and could get to web pages. Checked Exchange queues and saw mail going out. Asked what changed and he said they didn't do anything. We tested a few more things with good results and then closed the call. Client is happy but I wish I knew what changed so I know if I see this again. -Original Message- From: Charlie Kaiser [mailto:charl...@golden-eagle.org] Sent: Friday, May 01, 2009 8:23 AM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue How is external DNS set up? Forwarders? Root hints? I usually use forwarders. See if you can ping the listed forwarders; then try a Nslookup using those IPs as the server. Any firewall rules that might have been inadvertently changed? It sounds like DNS queries aren't getting replies from outside. Does internal DNS work? You might throw wireshark on the box and see what the DNS queries do... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:16 AM To: NT System Admin Issues Subject: Server 2003 DNS issue Have a client that is having trouble with Internet connectivity and Exchange sending mail externally. Has a SBS 2003 server up to date as of two weeks ago, nothing changed since then that I know of or can see. They can send and receive internal Exchange just fine. Receiving mail externally works fine. Outbound external mail is sitting in the queue. Error message is Unable to bind to the destination server in DNS. Opening IE displays the Page can not be found error message. Nothing in the event logs. Rebooted server, no effect. Ping by IP works. Ping by name doesn't. Error can not find server. Nslookup fails. Checked out several KB articles and all suggestions shown have been configured correctly on the server. Reran the Connect to Internet wizard, no change. Anyone have any ideas while I look some more. It really looks like DNS is broke on this box. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: Server 2003 DNS issue - Fixed
Sounds to me like they may have uploaded some changes to the DSL modem, and didn't want to admit they'd screwed things up originally. :-) Oh, well... all's well that ends well. :-) -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Monday, May 04, 2009 1:51 PM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue - Fixed I got this working but not exactly sure what made it start working. Called Qwest and they tested the lines and said things were working fine from their perspective. I figured that. Had the office reboot the DSL modem. They did this while I was connected since I lost connectivity. Logged back in and same error messages. While working remotely deleted DNS from the box, rebooted and reinstalled DNS. Ran SBS Connect to Internet wizard. Same problem. Checked everything again with other working SBS boxes and all settings were correct. Frustrated quit and went out and worked on my car. Saturday morning went to the office with my laptop. Checked everything locally just in case being remote was an issue. Same error messages. Configured laptop with server wan settings, connected to the DSL modem and same error messages. What! Must be a Qwest issue somewhere. Called Qwest support and tried to explain what was happening and what I had determined to the woman. Went through the basic support steps and she said it was a server issue. Uh no it wasn't could you check with someone else. On hold for a while, line got disconnected, waited five minutes with no call back and called in again. Got a different tech this time but he actually knew what I was talking about. Went through the basic support steps again with the same result. Put on hold while he went to check on some things and talk with another tech. Things didn't make sense so we started from the beginning again with the basic support steps. After rebooting the DSL modem, open command prompt, ping by IP working. Ping by name working. OK what changed. Open IE and could get to web pages. Checked Exchange queues and saw mail going out. Asked what changed and he said they didn't do anything. We tested a few more things with good results and then closed the call. Client is happy but I wish I knew what changed so I know if I see this again. -Original Message- From: Charlie Kaiser [mailto:charl...@golden-eagle.org] Sent: Friday, May 01, 2009 8:23 AM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue How is external DNS set up? Forwarders? Root hints? I usually use forwarders. See if you can ping the listed forwarders; then try a Nslookup using those IPs as the server. Any firewall rules that might have been inadvertently changed? It sounds like DNS queries aren't getting replies from outside. Does internal DNS work? You might throw wireshark on the box and see what the DNS queries do... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:16 AM To: NT System Admin Issues Subject: Server 2003 DNS issue Have a client that is having trouble with Internet connectivity and Exchange sending mail externally. Has a SBS 2003 server up to date as of two weeks ago, nothing changed since then that I know of or can see. They can send and receive internal Exchange just fine. Receiving mail externally works fine. Outbound external mail is sitting in the queue. Error message is Unable to bind to the destination server in DNS. Opening IE displays the Page can not be found error message. Nothing in the event logs. Rebooted server, no effect. Ping by IP works. Ping by name doesn't. Error can not find server. Nslookup fails. Checked out several KB articles and all suggestions shown have been configured correctly on the server. Reran the Connect to Internet wizard, no change. Anyone have any ideas while I look some more. It really looks like DNS is broke on this box. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.323 / Virus Database: 270.12.17/2095 - Release Date: 05/04/09 06:00:00 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
Re: Server 2003 DNS issue - Fixed
+1 I've had Comcast screw me on at least three occasions that way. If you have to reboot your modem its because the provisioning isn't matching their equipment or security configs. End of story. -- ME2 On Mon, May 4, 2009 at 2:06 PM, John Aldrich jaldr...@blueridgecarpet.comwrote: Sounds to me like they may have uploaded some changes to the DSL modem, and didn't want to admit they'd screwed things up originally. :-) Oh, well... all's well that ends well. :-) -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Monday, May 04, 2009 1:51 PM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue - Fixed I got this working but not exactly sure what made it start working. Called Qwest and they tested the lines and said things were working fine from their perspective. I figured that. Had the office reboot the DSL modem. They did this while I was connected since I lost connectivity. Logged back in and same error messages. While working remotely deleted DNS from the box, rebooted and reinstalled DNS. Ran SBS Connect to Internet wizard. Same problem. Checked everything again with other working SBS boxes and all settings were correct. Frustrated quit and went out and worked on my car. Saturday morning went to the office with my laptop. Checked everything locally just in case being remote was an issue. Same error messages. Configured laptop with server wan settings, connected to the DSL modem and same error messages. What! Must be a Qwest issue somewhere. Called Qwest support and tried to explain what was happening and what I had determined to the woman. Went through the basic support steps and she said it was a server issue. Uh no it wasn't could you check with someone else. On hold for a while, line got disconnected, waited five minutes with no call back and called in again. Got a different tech this time but he actually knew what I was talking about. Went through the basic support steps again with the same result. Put on hold while he went to check on some things and talk with another tech. Things didn't make sense so we started from the beginning again with the basic support steps. After rebooting the DSL modem, open command prompt, ping by IP working. Ping by name working. OK what changed. Open IE and could get to web pages. Checked Exchange queues and saw mail going out. Asked what changed and he said they didn't do anything. We tested a few more things with good results and then closed the call. Client is happy but I wish I knew what changed so I know if I see this again. -Original Message- From: Charlie Kaiser [mailto:charl...@golden-eagle.org] Sent: Friday, May 01, 2009 8:23 AM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue How is external DNS set up? Forwarders? Root hints? I usually use forwarders. See if you can ping the listed forwarders; then try a Nslookup using those IPs as the server. Any firewall rules that might have been inadvertently changed? It sounds like DNS queries aren't getting replies from outside. Does internal DNS work? You might throw wireshark on the box and see what the DNS queries do... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:16 AM To: NT System Admin Issues Subject: Server 2003 DNS issue Have a client that is having trouble with Internet connectivity and Exchange sending mail externally. Has a SBS 2003 server up to date as of two weeks ago, nothing changed since then that I know of or can see. They can send and receive internal Exchange just fine. Receiving mail externally works fine. Outbound external mail is sitting in the queue. Error message is Unable to bind to the destination server in DNS. Opening IE displays the Page can not be found error message. Nothing in the event logs. Rebooted server, no effect. Ping by IP works. Ping by name doesn't. Error can not find server. Nslookup fails. Checked out several KB articles and all suggestions shown have been configured correctly on the server. Reran the Connect to Internet wizard, no change. Anyone have any ideas while I look some more. It really looks like DNS is broke on this box. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.323 / Virus Database: 270.12.17/2095 - Release Date: 05/04/09 06:00:00 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise
RE: Server 2003 DNS issue - Fixed
I spent two days once trying to convince Insight communications that the problem was on their end. no, our equipment is fine, the issue is your server. My server was off and I was using their DHCP. Finally got someone on the line that knew more than reading que-cards. He fixed the DNS settings and boom... problem solved. Bob Fronk From: Micheal Espinola Jr [mailto:michealespin...@gmail.com] Sent: Monday, May 04, 2009 2:16 PM To: NT System Admin Issues Subject: Re: Server 2003 DNS issue - Fixed +1 I've had Comcast screw me on at least three occasions that way. If you have to reboot your modem its because the provisioning isn't matching their equipment or security configs. End of story. -- ME2 On Mon, May 4, 2009 at 2:06 PM, John Aldrich jaldr...@blueridgecarpet.commailto:jaldr...@blueridgecarpet.com wrote: Sounds to me like they may have uploaded some changes to the DSL modem, and didn't want to admit they'd screwed things up originally. :-) Oh, well... all's well that ends well. :-) -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.netmailto:art.dekn...@cox.net] Sent: Monday, May 04, 2009 1:51 PM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue - Fixed I got this working but not exactly sure what made it start working. Called Qwest and they tested the lines and said things were working fine from their perspective. I figured that. Had the office reboot the DSL modem. They did this while I was connected since I lost connectivity. Logged back in and same error messages. While working remotely deleted DNS from the box, rebooted and reinstalled DNS. Ran SBS Connect to Internet wizard. Same problem. Checked everything again with other working SBS boxes and all settings were correct. Frustrated quit and went out and worked on my car. Saturday morning went to the office with my laptop. Checked everything locally just in case being remote was an issue. Same error messages. Configured laptop with server wan settings, connected to the DSL modem and same error messages. What! Must be a Qwest issue somewhere. Called Qwest support and tried to explain what was happening and what I had determined to the woman. Went through the basic support steps and she said it was a server issue. Uh no it wasn't could you check with someone else. On hold for a while, line got disconnected, waited five minutes with no call back and called in again. Got a different tech this time but he actually knew what I was talking about. Went through the basic support steps again with the same result. Put on hold while he went to check on some things and talk with another tech. Things didn't make sense so we started from the beginning again with the basic support steps. After rebooting the DSL modem, open command prompt, ping by IP working. Ping by name working. OK what changed. Open IE and could get to web pages. Checked Exchange queues and saw mail going out. Asked what changed and he said they didn't do anything. We tested a few more things with good results and then closed the call. Client is happy but I wish I knew what changed so I know if I see this again. -Original Message- From: Charlie Kaiser [mailto:charl...@golden-eagle.orgmailto:charl...@golden-eagle.org] Sent: Friday, May 01, 2009 8:23 AM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue How is external DNS set up? Forwarders? Root hints? I usually use forwarders. See if you can ping the listed forwarders; then try a Nslookup using those IPs as the server. Any firewall rules that might have been inadvertently changed? It sounds like DNS queries aren't getting replies from outside. Does internal DNS work? You might throw wireshark on the box and see what the DNS queries do... *** Charlie Kaiser charl...@golden-eagle.orgmailto:charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.netmailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:16 AM To: NT System Admin Issues Subject: Server 2003 DNS issue Have a client that is having trouble with Internet connectivity and Exchange sending mail externally. Has a SBS 2003 server up to date as of two weeks ago, nothing changed since then that I know of or can see. They can send and receive internal Exchange just fine. Receiving mail externally works fine. Outbound external mail is sitting in the queue. Error message is Unable to bind to the destination server in DNS. Opening IE displays the Page can not be found error message. Nothing in the event logs. Rebooted server, no effect. Ping by IP works. Ping by name doesn't. Error can not find server. Nslookup fails. Checked out several KB articles and all suggestions shown have been configured correctly on the server. Reran the Connect to Internet wizard, no change. Anyone have any ideas while I look some more. It really looks like DNS is broke on this box. Thanks
RE: Server 2003 DNS issue
How is external DNS set up? Forwarders? Root hints? I usually use forwarders. See if you can ping the listed forwarders; then try a Nslookup using those IPs as the server. Any firewall rules that might have been inadvertently changed? It sounds like DNS queries aren't getting replies from outside. Does internal DNS work? You might throw wireshark on the box and see what the DNS queries do... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:16 AM To: NT System Admin Issues Subject: Server 2003 DNS issue Have a client that is having trouble with Internet connectivity and Exchange sending mail externally. Has a SBS 2003 server up to date as of two weeks ago, nothing changed since then that I know of or can see. They can send and receive internal Exchange just fine. Receiving mail externally works fine. Outbound external mail is sitting in the queue. Error message is Unable to bind to the destination server in DNS. Opening IE displays the Page can not be found error message. Nothing in the event logs. Rebooted server, no effect. Ping by IP works. Ping by name doesn't. Error can not find server. Nslookup fails. Checked out several KB articles and all suggestions shown have been configured correctly on the server. Reran the Connect to Internet wizard, no change. Anyone have any ideas while I look some more. It really looks like DNS is broke on this box. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: Server 2003 DNS issue
Forgot to mention. DNS is set to use Forwarders. Originally had Qwest DNS servers and switched to OpenDNS servers. Same result. I can ping forwarders by IP but not by name. No firewall rules changed. Internal DNS works fine. Ping a workstation by name and it resolves. I'll see what Netmon shows. -Original Message- From: Charlie Kaiser [mailto:charl...@golden-eagle.org] Sent: Friday, May 01, 2009 8:23 AM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue How is external DNS set up? Forwarders? Root hints? I usually use forwarders. See if you can ping the listed forwarders; then try a Nslookup using those IPs as the server. Any firewall rules that might have been inadvertently changed? It sounds like DNS queries aren't getting replies from outside. Does internal DNS work? You might throw wireshark on the box and see what the DNS queries do... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:16 AM To: NT System Admin Issues Subject: Server 2003 DNS issue Have a client that is having trouble with Internet connectivity and Exchange sending mail externally. Has a SBS 2003 server up to date as of two weeks ago, nothing changed since then that I know of or can see. They can send and receive internal Exchange just fine. Receiving mail externally works fine. Outbound external mail is sitting in the queue. Error message is Unable to bind to the destination server in DNS. Opening IE displays the Page can not be found error message. Nothing in the event logs. Rebooted server, no effect. Ping by IP works. Ping by name doesn't. Error can not find server. Nslookup fails. Checked out several KB articles and all suggestions shown have been configured correctly on the server. Reran the Connect to Internet wizard, no change. Anyone have any ideas while I look some more. It really looks like DNS is broke on this box. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: Server 2003 DNS issue
Can you do NSLookup and set server=the external server IP and get a DNS query reply? If not, the firewall may well be blocking the DNS traffic. What DNS servers are you using? Send an IP and I'll try a query from here to make sure the server is working... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:35 AM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue Forgot to mention. DNS is set to use Forwarders. Originally had Qwest DNS servers and switched to OpenDNS servers. Same result. I can ping forwarders by IP but not by name. No firewall rules changed. Internal DNS works fine. Ping a workstation by name and it resolves. I'll see what Netmon shows. -Original Message- From: Charlie Kaiser [mailto:charl...@golden-eagle.org] Sent: Friday, May 01, 2009 8:23 AM To: NT System Admin Issues Subject: RE: Server 2003 DNS issue How is external DNS set up? Forwarders? Root hints? I usually use forwarders. See if you can ping the listed forwarders; then try a Nslookup using those IPs as the server. Any firewall rules that might have been inadvertently changed? It sounds like DNS queries aren't getting replies from outside. Does internal DNS work? You might throw wireshark on the box and see what the DNS queries do... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Art DeKneef [mailto:art.dekn...@cox.net] Sent: Friday, May 01, 2009 8:16 AM To: NT System Admin Issues Subject: Server 2003 DNS issue Have a client that is having trouble with Internet connectivity and Exchange sending mail externally. Has a SBS 2003 server up to date as of two weeks ago, nothing changed since then that I know of or can see. They can send and receive internal Exchange just fine. Receiving mail externally works fine. Outbound external mail is sitting in the queue. Error message is Unable to bind to the destination server in DNS. Opening IE displays the Page can not be found error message. Nothing in the event logs. Rebooted server, no effect. Ping by IP works. Ping by name doesn't. Error can not find server. Nslookup fails. Checked out several KB articles and all suggestions shown have been configured correctly on the server. Reran the Connect to Internet wizard, no change. Anyone have any ideas while I look some more. It really looks like DNS is broke on this box. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
