RE: DNS problems after installing Server 2003 SP2
- From: v-robeli@xxxxxxxxxxxxxxxxxxxx (Robert Li [MSFT])
- Date: Thu, 29 Mar 2007 07:59:54 GMT
Hi,
Thanks for posting in our newsgroup.
Based on my research, after installing Windows 2003 Service Pack 2 on SBS
2003 with ISA 2004 installed, you may experience the following problems:
-You can no longer successfully connect inbound using VPN (Clients get
"Error 800: Unable to establish connection").
-You cannot reliably connect to the Internet using SecureNat.
-Some Outlook clients will fail to connect to the Exchange server (even
with ISA 2004 SP2 and KB930414 installed).
The problem may be related to Receive Side Scaling of SP2. You can disable
this feature from the advanced properties of the network card under the
network interface properties or you can perform the registry changes
provided below.
You can disable the RSS support from the TCP/IP stack by doing the
following:
Warning Serious problems might occur if you modify the registry incorrectly
by using Registry Editor or by using another method. These problems might
require that you reinstall the operating system. Microsoft cannot guarantee
that these problems can be solved. Modify the registry at your own risk.
To work around this problem, disable Receive Side Scaling when the computer
is configured as an Internet Connection Sharing gateway. To do this, follow
these steps:
1. Click Start, click Run, type regedit , and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, point to New, click DWORD Value, and then type
EnableRSS .
4. Double-click EnableRSS, type 0 , and then click OK.
5. Exit Registry Editor.
If you are still experiencing problems (like slow file copying), you should
also disable Offloading support:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. In the right pane, make sure that the DisableTaskOffload registry entry
exists. If this entry does not exist, follow these steps to add the entry:
a. On the Edit menu, point to New, and then click DWORD Value, and then
type DisableTaskOffload .
4. Double-Click DisableTaskOffload, type 1, and then click OK.
5. Exit Registry Editor.
(Reboot to make both changes effective)
If the problem cannot be resolved, please try to rerun the CEICW, the tool
helps us to configure the network and IIS settings:
To do this:
1. Click Start, click Server Management. Click To Do List and then click
"Connect to the Internet". Click Next, and go through the Internet option.
2. Select Enable firewall and click Next. Click the service you want to
publish.
3. On the Web Services Configuration page shows, select the website to you
want to visit from Internet. Click Next.
4. On the Web Server Certificate page shows. Select "Create a new Web
server certificate", and type your FQDN (mail.domain.com) in the "Web
server name" text box. Click Next.
IMPORTANT: The FQDN that you type in the "Web server name" box must be the
same name that you use to connect to the Web site from the Internet. For
example, if the URL that you use to connect to the RWW is
https://server.contoso.com/remote, type "server.contoso.com" (without the
quotation marks) in the "Web server name" box. If you use
http://ipaddress/remote to access RWW, type the public IP address in the
"Web server name".
5. Go through the steps to finish the wizard.
For more information, please refer to:
825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763
If the problem still exists, please kindly help me collect the following
information for further research:
1. Download the MPSRPT_NETWORK.EXE from the following link and then run
this tool to gather some information from the problematic computer:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE
2. Double-click on the MPSRPT_NETWORK.EXE file.
[Note] This process may take some time; however, it will not have a
negative effect on the performance.
3. A CAB file will be generated in the
%systemroot%\MPSReports\Network\Reports\Cab directory called
%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool.
4. Please send the CAB to SBSCDATA@xxxxxxxxxxxxx with
subject:Windowsserver.sbs: 38509340-DNS problems after installing Server
2003 SP2
If you need further assistance, please don't hesitate to let me know.
Best regards,
Robert Li(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.
--------------------
<Thread-Topic: DNS problems after installing Server 2003 SP2
<thread-index: Acdw3D0E81+yTHzNTuiIfXUPDqN8NA==
<X-WBNR-Posting-Host: 207.46.19.168
<From: =?Utf-8?B?V2FsZGVtYXIgS2lsaXM=?=
<WaldemarKilis@xxxxxxxxxxxxxxxxxxxxxxxxx>
<Subject: DNS problems after installing Server 2003 SP2
<Date: Tue, 27 Mar 2007 18:56:02 -0700
<Lines: 13
<Message-ID: <80E21D51-9BC4-4235-B928-9F721821871D@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:25860
<NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<I run SBS 2003 Premium Edition with Exchange server and a company web site
on
<the same box. After installing Windows Server 2003 SP2, the DNS does not
<seem to be responding to external DNS queries making the Exchange server
and
<web site inaccessible to the Internet. If I use nslookup with any other
DNS
<server than my own, querying my domain produces a timeout.
<
<I can connect to the OWA page with public IP address, which tells me that
<both email server and IIS are running properly. I've checked ISA logs
and
<UDP port 53 packets are allowed. Also, DNS server works on internally.
<
<Any idea how to troubleshoot this problem? I'm becoming desperate for a
<solution. If unninstalling SP2 would fix the problem, I would do it. Any
<advice?
<
.
- Prev by Date: 'Users' share only visible on server
- Next by Date: Re: VPN drops
- Previous by thread: Re: DNS problems after installing Server 2003 SP2
- Next by thread: Re: dhcp query
- Index(es):
Relevant Pages
|
