RE: Microsoft Windows SBS 2003 Communication Issues

I did the steps 1-6 and the two new policies did not show up.


--
Dave


""Jenny wu [MSFT]"" wrote:

> Hi Dave,
>
> To the event W32Time 29 event error, I suggest you follow below steps to
> see if it helps.
>
> I. Make sure that the Time service on the SBS 2003 server is enabled.
>
> For the SBS server, the time server may be disabled by some software.
> Please try the following steps to enable the time service on the SBS server:
>
> 1. Open Services console in 'Administrative Tools'.
>
> 2. Double-click Windows Time service. Change the startup type from Disable
> to Automatic.
>
> 3. Open Registry editor (regedit); navigate to the following registry:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\
>
> Double-click 'Type' value in the right panel. Change the value data from
> NoSync to NT5DS
>
> 4. Go to the service console, double-click the Windows Time service and
> click 'Start' button to start the service.
>
> The above steps will make the server to respond the internal time synch
> requests. Go to the Windows XP workstation, open a command prompt, run the
> following command to perform a test:
>
> w32tm /monitor /computers:localhost
>
> [ex]. C:\>w32tm /monitor /computers:localhost
> localhost [127.0.0.1]:
> ICMP: 0ms delay.
> NTP: +0.0000000s offset from local clock
> RefID: ntdev-dc-10.ntdev.microsoft.com [x.x.x.x]
> The computer returned on the RefID line is the time server with whom the
> client is synchronizing its time.
>
> II. For ISA server is installed on the SBS box, ensure that the packet
> filters for time synchronization has been properly configured:
> 1. In the ISA Server management tool, expand the management nodes that are
> beneath your server name.
>
> 2. Expand the Access Policy branch to view the list of access policies.
>
> 3. Right-click IP Packet Filters, point to New, and then click Filter to
> start the New IP Packet Filter Wizard.
>
> 4. Type a descriptive name for the filter (such as "SNTP Allow Filter"
> (without the quotation marks)), and then click Next.
>
> 5. Click Allow packet transmission as the Filter Mode, and then click Next.
>
> 6. Click Custom as the filter type, and then click Next.
>
> 7. On the Filter Settings page, click UDP for the IP protocol, click "Send
> receive" for the direction, "All ports" as the local port, click "Fixed
> port" as the remote port, use port 123 as the remote port number, and then
> click Next.
>
> 8. Keep the default settings by clicking Next through the next two wizard
> pages, and then click Finish at the Completing The New IP Packet Filter
> Wizard page.
>
> 9. Go to Monitoring\Services and restart the Firewall service. Check if the
> issue disappears.
>
> For more info, see:
> 323621 How To Configure the Simple Network Time Protocol (SNTP) on ISA
> Server
> http://support.microsoft.com/?id=323621
>
> III. Reconfigure the Windows time service
> Open a command prompt and run the following commands to re-configure the
> time service to sync time with time.nist.gov:
>
> w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
>
> w32tm /config /update
>
> net stop w32time
>
> net start w32time
>
> And then please try to test to see if the error event disappears.
>
> Hope above information helps! I am happy to be assistance of you.
>
> Have a nice day!
>
> Sincerely,
>
> Jenny Wu
> 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.
>
> --------------------
> >X-Tomcat-ID: 186062537
> >References: <26ED9605-6F08-454C-B1F5-7DA15A4B90C2@xxxxxxxxxxxxx>
> <JOwj2#J$FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
> <7A919C2A-7E61-4583-A05E-7AADA2E2B434@xxxxxxxxxxxxx>
> <ky2ys5w$FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
> <69AE4FDA-44B2-4E09-921A-2C58332F7E42@xxxxxxxxxxxxx>
> <t5turZ8$FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
> <B73A72B6-7CF2-4B19-8124-457F2FF4F3D2@xxxxxxxxxxxxx>
> <KALOJXIAGHA.1236@xxxxxxxxxxxxxxxxxxxxx>
> <9BDB1A3C-15A0-486E-9E8C-01751175C808@xxxxxxxxxxxxx>
> <9xK$d#RAGHA.2900@xxxxxxxxxxxxxxxxxxxxx>
> <25AA4B21-C43F-473D-AB46-B7B5AE45DBDC@xxxxxxxxxxxxx>
> <4rpCRqeAGHA.832@xxxxxxxxxxxxxxxxxxxxx>
> <51dJEYhAGHA.2540@xxxxxxxxxxxxxxxxxxxxx>
> <C9D1CD59-6E30-4028-88D4-0765F02C8819@xxxxxxxxxxxxx>
> <zgL2V7FBGHA.2560@xxxxxxxxxxxxxxxxxxxxx>
> <A5F706C1-621A-4102-A75D-62DAB81E2EEC@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain
> >Content-Transfer-Encoding: 7bit
> >From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
> >Organization: Microsoft
> >Date: Wed, 21 Dec 2005 10:30:38 GMT
> >Subject: RE: Microsoft Windows SBS 2003 Communication Issues
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >Message-ID: <xE#vkmhBGHA.3096@xxxxxxxxxxxxxxxxxxxxx>
> >Newsgroups: microsoft.public.windows.server.sbs
> >Lines: 449
> >Path: TK2MSFTNGXA02.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:231682
> >NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
> >
> >Hi Dave,
> >
> >Thanks for your information by mail.
> >
> >Please note that 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.
> >
> >Let"s focus on the group policy issue first. Please follow below steps to
> >edit the System.adm file to see if the issue be fixed.
> >
> >1. Please open the system.adm file in Notepad (or other text edit tool)
> >under the following location:
> >
> >C:\WINDOWS\SYSVOL\sysvol\yourdomainname.local\Policies\{31B2F340-016D-11D2-
> 9
> >45F-00C04FB984F9}\Adm
> >
> >*Note: Please change the "yourdomainname.local" to your true domain name.
> >
> >
> >2. Find the following lines (should be 4 changes in total):
> >
> > #if version >= 5
> > POLICY !!WF_AllowedPrograms_Name
> >
> > #if version >= 5
> > POLICY !!WF_OpenPorts_Name
> >
> >3. Change just the number 5 to a 3 for all instances.
> >
> >Note: There should be should be 4 changes in total: 2 instances of
> >WF_AllowedPrograms_Name, and 2 instances of WF_OpenPorts_Name, as these
> >policy settings exist under both the "Domain Profile" and "Standard
> >Profile" subfolders.
> >
> >4. Save the changes in the System.adm file.
> >
> >5. Open the default domain policy and reload the System.adm file
> >(right-click Administrative Templates, choose Add/Remove Templates, remove
> >System item and then re-add it back using the changed System.adm file for
> >the above changes to take effect.
> >
> >*Note: Please ensure you have load the System.adm file in appropriate
> >location
> >(C:\WINDOWS\SYSVOL\sysvol\yourdomainname.local\Policies\{31B2F340-016D-11D2
> -
> >945F-00C04FB984F9}\Adm)
> >
> >6. Open command line, run command "gpupdate /force" (no quotation marks)
> >and then open the GPO to see if the both the settings (Windows Firewall:
> >Define program exceptions; Windows Firewall: Define port exceptions)
> >showing up.
> >
> >I appreciate your time! I am happy to be assistance of you!
> >
> >Have a nice day!
> >
> >Sincerely,
> >
> >Jenny Wu
> >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: Microsoft Windows SBS 2003 Communication Issues
> >>thread-index: AcYFsfxdLUhuqMnzTtC0ksZdnDeptw==
> >>X-WBNR-Posting-Host: 65.105.239.66
> >>From: "=?Utf-8?B?RGF2ZQ==?=" <Dave@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>References: <26ED9605-6F08-454C-B1F5-7DA15A4B90C2@xxxxxxxxxxxxx>
> ><JOwj2#J$FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
> ><7A919C2A-7E61-4583-A05E-7AADA2E2B434@xxxxxxxxxxxxx>
> ><ky2ys5w$FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
> ><69AE4FDA-44B2-4E09-921A-2C58332F7E42@xxxxxxxxxxxxx>
> ><t5turZ8$FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
> ><B73A72B6-7CF2-4B19-8124-457F2FF4F3D2@xxxxxxxxxxxxx>
> ><KALOJXIAGHA.1236@xxxxxxxxxxxxxxxxxxxxx>
> ><9BDB1A3C-15A0-486E-9E8C-01751175C808@xxxxxxxxxxxxx>
> ><9xK$d#RAGHA.2900@xxxxxxxxxxxxxxxxxxxxx>
> ><25AA4B21-C43F-473D-AB46-B7B5AE45DBDC@xxxxxxxxxxxxx>
> ><4rpCRqeAGHA.832@xxxxxxxxxxxxxxxxxxxxx>
> ><51dJEYhAGHA.2540@xxxxxxxxxxxxxxxxxxxxx>
> ><C9D1CD59-6E30-4028-88D4-0765F02C8819@xxxxxxxxxxxxx>
> ><zgL2V7FBGHA.2560@xxxxxxxxxxxxxxxxxxxxx>
> >>Subject: RE: Microsoft Windows SBS 2003 Communication Issues
> >>Date: Tue, 20 Dec 2005 14:09:02 -0800
> >>Lines: 316
> >>Message-ID: <A5F706C1-621A-4102-A75D-62DAB81E2EEC@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.0
> >>Newsgroups: microsoft.public.windows.server.sbs
> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:231512
> >>X-Tomcat-NG: microsoft.public.windows.server.sbs
> >>
> >>I recreated it on another users PC and here are some of the errors that
> >came
> >>up under Event Viewer
> >>32026
> >>32068
> >>MS Fax - I can see a fax on the SBS server but we don't use it
> >>59
> >>sidebyside
> >>29
> >>W32Time
> >>
> >>--
> >>Dave
> >>
> >>
> >>""Jenny wu [MSFT]"" wrote:
.