Re: Massivly slow internet connection

Hello Tim,

Thank you for posting.

>From your post, my understanding of this issue is: After running the
"Connect to the Internet" wizard to change the preferred DNS server, the
Internet connections becomes very slow on all client computers. If this is
not correct, please feel free to let me know.

First I would thanks for Lanwench's kind inputs. He provided useful
information for us, and you may configure the DNS server and forwarder
settings as his suggestion. In addition, the Default Gateway settings on
all client computers and SBS Server should be pointed to the LAN port of
the router.

If the issue still exists, we may need to perform some test to narrow down
the root cause of this issue. We can configure the DNS setting on one
client computer to change the prefer DNS server to the external DNS server,
and then try to open some Internet web sites to test the connection speed.

If the Internet connection speed is still slow on this client computer,
this issue may has nothing to do with the SBS Server. We may need to check
the router/firewall, and I suggest also scan the computers for virus.

If the Internet connection speed is normal on this client computer, we may
perform the following steps for a test:

1. On the SBS 2003 Server, install the Dnscmd.exe program from the SBS 2003
Support Tools. To install the Windows Support Tools, right-click
"Suptools.msi" in the Support\Tools folder on the SBS 2003 CD-ROM, and then
click "Install". Follow the steps in the Windows Support Tools Setup
Wizard to complete the installation of the Windows Support Tools.

2. At a command prompt, type the following command, and then press ENTER:

"dnscmd /config /enableednsprobes 0" (without the quotation marks)
Note: Type a "0" (without the quotation marks) (zero) and not the letter
"O" after "enableednsprobes" in this command.

The following information appears:
Registry property enableednsprobes successfully reset.
Command completed successfully.

This issue may be caused by the Extension Mechanisms for DNS (EDNS0)
functionality that is supported in Windows Server 2003 DNS. ENDS0 permits
the use of larger User Datagram Protocol (UDP) packet sizes. However, some
firewall programs may not permit UDP packets that are larger than 512
bytes. As a result, these DNS packets may be blocked by the firewall.

After you run this command, Windows Server 2003 DNS no longer advertises
its EDNS0 capabilities. As a result, the Windows Server 2003 DNS server
will not be sent UDP packets that are larger than 512 bytes. For detailed
information about this issue, please refer to the following KB article:

Some DNS Name Queries Are Unsuccessful After You Upgrade Your DNS Server to
Windows Server 2003
http://support.microsoft.com/?id=832223

An external DNS query may cause an error message in Windows Server 2003
http://support.microsoft.com/?id=828731

If the issue still occurs, please help me to collect some information about
your network configurations. Please perform the following steps on the SBS
server and one of the client computer, and send the results files to me at
v-stwang@xxxxxxxxxxxxx, so that I can perform further research on this
issue:

1. Collect Netdiag logs:
------------------------------------
a. Click Start, click Run, type cmd, and then click OK.
b. Type "cd \", press Enter, type "netdiag /v /l" (without the quotation
marks), press Enter.
c. Please send the C:\netdiag.log file to me.

2. Collect DNS Debug log:
------------------------------------
a. Open DNS.
b. In the console tree, right-click the applicable DNS server, then click
Properties.
c. Click the Debug Logging tab.
d. Select Log packets for debugging, and then select all the events that
the DNS server to record for debug logging.

Notes
- To perform this procedure, you must be a member of the Administrators
group on the local computer, or you must have been delegated the
appropriate authority.
- To open DNS, click Start, click Control Panel, double-click
Administrative Tools, and then double-click DNS.
- To set the debug logging options, you must first select Log packets for
debugging.
- To get useful debug logging output you need to select a Packet direction,
a Transport protocol and at least one more option.
- In addition to selecting events for the DNS debug log file, you can
specify the file name, location, and maximum file size for the file.
- Using debug logging options slows DNS server performance. For this
reason, all debug logging options are disabled by default.

e. Open some web site on the server and client computers. After 1 or 2
hours, please stop the DNS debug logging and then send the DNS debug log
file to me. By default this file is located at
%systemroot%\System32\Dns\Dns.log.

Hope the above information helps. If anything is unclear or you have any
concern, please feel free to let me know. I look forward to hearing from
you soon.

Have a nice day!

Steven Wang (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>From: "Marina Roos [SBS-MVP]" <marina@xxxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <#jkisP5sFHA.3604@xxxxxxxxxxxxxxxxxxxx>
<OWMnFY7sFHA.2064@xxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Massivly slow internet connection
>Date: Thu, 8 Sep 2005 15:07:33 +0200
>Lines: 51
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
>Message-ID: <O7liLZHtFHA.4076@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: computerworks.xs4all.nl 213.84.106.4
>Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP1
1.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:203221
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>When only using 1 nic in the server, you want to make sure you have a
proper
>hardware firewall. That 510 is just a simple NAT router, nothing more. Use
2
>nics with this setup. Post the ipconfig/all from the server and one from a
>client.
>
>--
>Regards,
>
>Marina Roos
>Microsoft SBS-MVP
>One of the Magical M&M's
>www.smallbizserver.net
>Take part in SBS forum:
>http://www.smallbizserver.net/Default.aspx?tabid=53
>
>"Lanwench [MVP - Exchange]"
><lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> schreef in
>bericht news:OWMnFY7sFHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
>>
>>
>> In news:%23jkisP5sFHA.3604@xxxxxxxxxxxxxxxxxxxx,
>> Tim <Wingeronside@xxxxxxx> typed:
>> > Hi,
>> >
>> > I ran the 'Connect to the Internet' wizard again today, this time
>> > changing my prefered DNS to my domain hosting IP addresses. Since
>> > this all my client computers have has massivly slow internet
>> > connections, below 56k speeds! Also sites like e-bay.co.uk fail to
>> > load.
>> > Have I set something up wrong here? The domain is www.timsweb.net
>> >
>> > System setup:
>> > 4 Clients
>> > 1 SBS server
>> > I Speedtouch 510 ADSL
>> >
>> > Server has one network card connecting it to the router, as do all
>> > the other clients. (I know it should have 2 but one was easier)
>>
>> I personally prefer a single NIC in a domain controller. If you aren't
>> running ISA, or the Windows firewall, you don't actually *need* two.
>>
>> Everyone needs to be pointing *only* at the SBS server's LAN IP for DNS -
>no
>> external DNS server IPs should be in the clients or in the server's IP
>> config itself. Use forwarders to your ISP's DNS server, in the DNS server
>> properties itself, or use root hints only. I use both.
>>
>>
>
>
>

.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... DNS stuff says your mail server is responding with reply that is not MS ... When we setup this new SBS2003 setup we installed without ISA as it does ... not seeing any problems anywhere regards internet or email - we also run ...
    (microsoft.public.windows.server.sbs)
  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)
  • Re: resolve incorrect IP from RRA server.
    ... dynamic address, 10.5.101.123 from DHCP server. ... This is because the addtional DNS records that get registered cause major problems with AD functionality, especially the additional IPs registered by RRAS. ... However, if you choose to keep RRAS on the DC, then you have to force DNS to only register the internal static interface, and no others. ... If it is the internet gateway, it is recommended to purchase an inexpensive, or cable/DLS router, or even better, a Cisco or similar firewall to perform the task, which if it is compromised by an internet attacker remotely, can further compromise the rest of the internal network. ...
    (microsoft.public.windows.server.dns)
  • Re: Urgent! New router and big disaster
    ... Even a single-NIC configuration should have ONLY the LAN IP of the server as ... Then you can run the CEICW or use the DNS console to enter ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)