v-gzwang
Tue Jul 01 02:45:24 PDT 2008
Hello Customer,
Thank you for your post and thanks for Joe's great help.
My name is Gary Wang, and it is my pleasure to work with you on this issue!
Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:
2 of your SBS clients cannot connect to internet.
If I have misunderstood your concerns please feel free to let me know.
Suggestion :
==============
I agree with Joe. Based on my experience, it is should not be related to
the server side. Besides his inputs, I would like to suggest that you check
the following steps:
1. Ensure the default gateway of the 2 clients point to router internal IP.
2. Disable windows firewall on the 2 problematic clients to test this issue.
3. Clean boot on the 2 problematic clients to test this issue.
Let's disable all startup items and third party services when booting. This
method will help us determine if this issue is caused by a loading program
or service. Please perform the following steps:
1. Click the Start Button type "msconfig" (without quotation marks) in the
Start Search box, and then press Enter.
Note: If prompted, please click Continue on the User Account Control (UAC)
window.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box
and click "Disable All" (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
Then, restart the computer. When the "System Configuration Utility" window
appears, please check the "Don't show this message or launch the System
Configuration Utility when Windows starts" box and click OK.
Please test this issue in the Clean Boot environment, if the issue
disappears in the Clean Boot environment, we can use a 50/50 approach to
quickly narrow down which entry is causing the issue.
For more information about this step, please refer to the following KB
article:
How to troubleshoot a problem by performing a clean boot in Windows Vista
http://support.microsoft.com//kb/929135
4. Can you access companyweb or OWA on SBS from the 2 problematic clients?
5. Can you access shared folder on the other good clients from the 2
problematic clients?
6. Perform a full scan for antivirus on problematic client to make sure the
OS is clean.
7.Check the proxy settings(if you are using).
8. Try to ping the router's internal IP address, what's the result?
If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:
Information Need
==============
1. Check event viewer on problematic clients, please help save it to *.evt
and send to me.
2. Run command "ipconfig /all > c:\ipconfig_sbs.txt" and "route print >
c:\route_sbs.txt" on SBS, send the files c:\ipconfig_sbs.txt and
c:\route_sbs.txt to me
3. Run command "ipconfig /all > c:\ipconfig_client.txt" and "route print >
c:\route_client.txt" on problematic client, send the files
c:\ipconfig_client.txt and c:\route_client.txt to me
My email address is v-gzwang@microsoft.com
I look forward to your reply. Also, if you have any questions or concerns,
please do not hesitate to let me know. I am happy to help. :-)
Thank you for your time and cooperation!
Best regards,
Gary 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.
--------------------
| Date: Mon, 30 Jun 2008 22:26:57 +0100
| From: Joe <joe@jretrading.com>
| User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509)
| MIME-Version: 1.0
| Subject: Re: Internet Connection Issues, clients...
| References: <1669F319-5593-4431-A8C9-2C9659AA224B@microsoft.com>
<eKGIjCu2IHA.5512@TK2MSFTNGP06.phx.gbl>
<90DA69B2-96C6-4064-A25C-45169B94D5F4@microsoft.com>
| In-Reply-To: <90DA69B2-96C6-4064-A25C-45169B94D5F4@microsoft.com>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <O8UAIgv2IHA.1436@TK2MSFTNGP05.phx.gbl>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: jretradingltd.demon.co.uk 80.177.211.93
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:113531
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| >
| >
| > "Joe" wrote:
| >
| >> JT wrote:
| >>> I have a computer connecting to our server/domain controller,
accessing
| >>> Exchange,
| >>> Access and other network related applications. All work without a
problem.
| >>>
| >>> As of recently, 2 computers on our network will not connect to the
web. They
| >>> obtains an IP address via the DHCP (internal) server and DNS
(internal) with
| >>> no issues but still can't connect to the web. When I try pining
external
| >>> domains or ip addresses, it times out. I've tried repairing the IP,
flushing
| >>> the DNS, stripping all
| >>> startup items, manually entering the ip address and DNS server
address and
| >>> switched it back to auto since that didn't resolve the issue. I've
searched
| >>> and can't find a solution. I thought maybe it could be the server but
the
| >>> server is functioning fine and serving 23 other users who are
connecting
| >>> through it's DHCP and DNS servers. We're using W2K3 SBS.
| >>>
| >>> Short of re-installing Windows XP on the work station, is there any
other
| >>> things I could try before going to that extreme?
| >>>
| >>> Thank you!
| >>>
| >>>
| >>>
| >> To know what is stopping access, we need to know what hardware and
| >> software obstacles an Internet connection has to negotiate. What
stands
| >> between the workstations and the Internet?
| >>
| >> In other words, the usual: are you using one NIC or two, if two, are
you
| >> using ISA, is there a router...?
| >>
| >>
| JT wrote:
| > One NIC on the server. The work station obtains it's DHCP lease from
| the SBS
| > server and SBS server is managing DNS. We have a firewall router
| (Netgear)
| > connected to a T1 line going out.
|
|
| So we can pretty much forget the SBS. As long as the client gets the IP
| address and gateway it should work, at least at the IP address level. We
| can forget DNS for the moment. Apart from OS corruption, unlikely in two
| machines simultaneously, that leaves more obscure stuff. The fact that
| two machines are doing it would seem to alter the probabilities of
| various kinds of faults, but coincidences do actually happen in real
| life. Still, the common features of the network are the first things to
| go for:
|
| Router hardware and internal connection tables. OK, it shouldn't
| discriminate against just two out of 25 machines, but then this
| shouldn't be happening at all. If the workstations can ping the router,
| and see its web management interface, but not see the Internet, it's a
| good suspect. If you haven't already, try rebooting it, by power cycle
| rather than software. While the OS code in Netgear routers is pretty
| reliable, I'm not impressed by their system firmware and fault resilience.
|
| Switch/hub and cabling, switch table corruption. Not all that likely,
| but again, reboot the switch. If at least one of the workstations is
| physically close enough e.g. in the same office, and the router has a
| spare port, try running a cable directly between them. If not, and
| nothing else helps, it might be worth pulling the router and one
| workstation cable from the main switch, and linking them with a small
| switch.
|
| NICs and drivers on the offending workstations. See if there are more
| recent drivers. Difficult to test a NIC without substitution, but
| unlikely for two to fail at once. Old drivers are a possibility, or even
| newly upgraded ones. Here's a way for two similar machines to fail
| together, after a Windows or driver update.
|
| Multiple copies of the same IP address. SBS usually spots that quickly
| if it's handling DHCP, but it's worth considering. Not very likely, but
| you may end up clutching at straws.
|
| Other troubleshooting possibilities are to connect a different computer
| at one of the offending locations, or to boot up a live-CD Linux on one
| of them, but it's easy to be misled by apparently clear-cut results when
| doing this kind of thing. More things are being changed and tested than
| you realise, right down to the cable leaving the RJ-45 at a different
| angle...
|
| There are probably many other possibilities as well, but this selection
| reflects my experience of odd problems. Please post back when you do
| sort this one out.
|