Re: Cannot connect to Server
- From: v-shshao@xxxxxxxxxxxxxxxxxxxx ("Shawn Shao [MSFT]")
- Date: Thu, 03 Jan 2008 09:40:23 GMT
Hi Etq,
Thank you for posting here and Larry's suggestions.
From your post, I understand that after moving the SBS server to a newplace, the SBS server cannot be pinged, some clients cannot get IP address
SBS either. If I have misunderstood the problem, please don't hesitate to
let me know.
Based on my experience, the ICMP package which is used by ping command may
have been blocked by Windows Firewall, group policies or some third party
programs. I suggest we try the following steps to see if we can resolve
this issue:
Step 1: Disable Windows firewall on SBS server
================
If the Windows firewall start on SBS, it will block the DHCP request
traffic from client computer to SBS. Of course it will block the clients
ping SBS. I suggest you check the Windows firewall state on SBS, and ensure
it has been stopped:
1. Run services.msc and open Services console.
2.. Find Windows Firewall\Internet Connection Sharing (ICS) service and
double-click it.
3. Select Disable in Startup type box.
4. Reboot SBS. Then, test this issue.
Step 2: Test this issue in a Clean Boot from the server
================
1. Click the Start menu and choose Run.
2. Type in "msconfig" (without the quotation marks) and click OK.
3. On the Startup page, click Disable All.
4. On the Services page, mark the checkbox before "Hide All Microsoft
Services" and then click Disable All.
5. Click Apply and click OK.
6. Restart the computer.
A dialog box will appear indicating that some changes have been applied to
Windows Configurations. Please mark the check box and then cancel this
dialog box.
Please check if the issue persists in Clean Boot mode.
Step 3: Check IPSEC policy configurations which can also block the ICMP
package
================
1. Logon SBS server, click Start, go to run, type rsop.msc in the box and
click OK
2. Go to Computer configuration\Windows Settings\Security settings\IPSEC
policies on local computer.
3. Please check if IPSEC policies are applied or not.
4. If IPSEC policies are applied, check if they are blocking ICMP traffic.
If so, please temporarily disable them in group policies and then try ping
command again.
5. Please also check if IPSEC policies are defined for client computers.
You may refer to this article for more information about IPSEC:
To assign or unassign IPSec policy in Group Policy
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-
us/ipsec_sec_pol_assign_domain_policy.mspx?mfr=true
If the issue still persists, please help collect the following information:
1. Can the SBS server access shared resource on the internal LAN? Can it
access internet? Can telnet work?
2. If you release the IP address on those client workstations that can get
IP address, then renew the IP address, will them get IP address again
without problem?
3. If you manually assign IP address for client workstation, will it work
well?
4. Please let me know the network topology.
5. Please help me collect the MPS reports from both problematic client and
SBS server for further research:
---------------
1. Download MPS Report tool from below URL:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_Network.EXE
2. Execute the tool on the computer, and if you are prompted "Include the
MSINFO32 report?", please type Y.
3. Please send the result file (CAB file) to me at v-shshao@xxxxxxxxxxxxxx
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Shawn Shao
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.
.
- Follow-Ups:
- Re: Cannot connect to Server
- From: etq
- Re: Cannot connect to Server
- References:
- Cannot connect to Server
- From: etq
- Re: Cannot connect to Server
- From: Larry Struckmeyer
- Re: Cannot connect to Server
- From: etq
- Re: Cannot connect to Server
- From: Larry Struckmeyer
- Re: Cannot connect to Server
- From: etq
- Cannot connect to Server
- Prev by Date: RE: MISSING PERFORMANCE COUNTERS
- Next by Date: Re: Exchange in Recovery Mode
- Previous by thread: Re: Cannot connect to Server
- Next by thread: Re: Cannot connect to Server
- Index(es):
Relevant Pages
|