Link to home
Start Free TrialLog in
Avatar of CraigWalkerAE
CraigWalkerAE

asked on

SBS2003 Offline Files popup all the time

Hi,

In April 2008 we bit the bullet and upgraded from our small P2P network to SBS2003.
We got a contractor to build and configure the server and install. Everything was fine until Xmas, when we had issues with DNS. I managed to resolve the issues (constantly kicking people off the network) but I introduced some Exchange issues, again I managed to resolve them but now there are few things that just dont seem right.

These small things are starting to become a little worse, I seem to be the most affected by these issues.

THE ISSUE:
I keep getting the offline files balloon pop up and therefore lose all network drives, I click OK to syncronise straight away and everything is fine. However this is happening more and more, and it has started to happen to more people now.

We all run Windows XP SP3; the only other hardware involved is a Netgear Gigabit switch that connects all clients (10-15) to server. This was a 100Mbit switch but was upgraded at Xmas (thats when we got problems). Switch is working fine I know there are no issues with that as same problems occur when I change back to 100Mbit one.

All help is greatly appreciated.
Avatar of suppsaws
suppsaws
Flag of Belgium image

Hello CraigWalkerAE,

did you upgrade the NIC drivers of the server/clients?
please post an ipconfig /all of the server + one client too, I want to check to see if dns is fine.

Regards,

suppsaws
Avatar of CraigWalkerAE
CraigWalkerAE

ASKER

Posted both in Code Snippet;

192.168.1.254 is our router which is DHCP enabled and serves that purpose.
SERVER;
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
 
C:\>ipconfig/all
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : ae-srv-01
   Primary Dns Suffix  . . . . . . . : AEDirectMail.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : AEDirectMail.local
 
Ethernet adapter Server Local Area Connection:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit Server A
dapter
   Physical Address. . . . . . . . . : 00-1E-0B-DD-53-C0
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254
   DNS Servers . . . . . . . . . . . : 192.168.1.254
                                       192.168.1.2
   Primary WINS Server . . . . . . . : 192.168.1.2
 
 
 
My Client;
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
 
H:\>ipconfig/all
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : Craig-PC
        Primary Dns Suffix  . . . . . . . : AEDirectMail.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : AEDirectMail.local
 
Ethernet adapter VMware Network Adapter VMnet8:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for
VMnet8
        Physical Address. . . . . . . . . : 00-50-56-C0-00-08
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.72.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
 
Ethernet adapter VMware Network Adapter VMnet1:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for
VMnet1
        Physical Address. . . . . . . . . : 00-50-56-C0-00-01
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.92.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
 
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Con
nection
        Physical Address. . . . . . . . . : 00-21-5A-76-B5-77
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.24
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.254
        DNS Servers . . . . . . . . . . . : 192.168.1.2
                                            192.168.1.254
        Primary WINS Server . . . . . . . : 192.168.1.2

Open in new window

And no, drivers are untouched on NIC.
ah, there lies the mistake.
cut off dhcp on the router, and let SBS be the dhcp server.
        DNS Servers . . . . . . . . . . . : 192.168.1.2
                                            192.168.1.254
the ONLY dns server on the clients should be the SBS server itself.
Then rerun the connect to the internet wiizard which will configure the dhcp scope on your server.
and off course driver updates are important too, certainly the NIC's. (and windows updates off course too)
I'll try that as soon as I can.
However as a little test could I just remove our routers DNS from my client. I have my IP set to static.
SOLUTION
Avatar of suppsaws
suppsaws
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
CraigWalkerAE,

btw, some interesting things can be found here: http://sbs.editme.com/getstarted

suppsaws
Thanks for your help so far suppsaws.

I have 2 questions;

Firstly, why did this work for 8 months without issues having the router as dhcp and not the server?

Secondly, I'm not entirely sure what I would put in the ISP DNS Server (Forwarders), do you know of a way I can find this out?
- well, I don't know the whole situation, so for me that is very difficult to diagnose since I didn't do the setup.
But, since dhcp is on the router the first mistake was made.
You cAn run dhcp on the router, but in an sbs network you really should run it on the sbs server itself.
secondly, the dns setup is wrong. a client should always point to the SBS as their only dns server.
The ISP dns servers can be found normally on the website of the isp, or by giving them a call.

btw, how were these clients joined to the network?
Manually by the team that installed the server.

After many hours of research and reading I know that they all should have used the web based connect computer wizard.

Which brings me to my next point. It seems like we received a bad setup, doing these changes you suggest does sound like a major change. Which would most probably have to be done at a weekend. Sounds like after I configure the server properly I will have to go round connecting each computer properly. Is there an easy way of doing this? How will the clients act if I just disconnect them from the server by deleting the computers from the Server Management/Computers?

BTW for others following this my ISP is BT and the DNS server are;
194.72.9.34
194.72.9.38
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thats a great tutorial, thanks.

1 last question, does the gateway stay at the router address of 192.168.1.254?
^^ gateway for the server
the gateway should be your router yes, see internet connection wizard + tutorial on the site
Hi Suppsaws,

I changed my client over and did the server work late on Friday. I will monitor my client over the next few days as this seemed to be the worst one. Then I will award the solution to you.

Thanks for your help so far..
Hi Suppsaws,

My machine wouldn't recognise any website names on Friday, rebooted this morning and its exactly the same.

I have had to manually input my DNS servers;
192.168.1.2 (SBS)
192.168.1.254 (Router)

I now have functional DNS for websites (how I am able to get here).

I'm thinking there are DNS issues on the SBS?

When I do "NSLOOKUP ae-srv-01" I get the following;


H:\>NSLOOKUP ae-srv-01
*** Can't find server name for address 192.168.1.2: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.1.2
 
Name:    ae-srv-01.AEDirectMail.local
Address:  192.168.1.2

Open in new window

If I do the NSLOOKUP whilst having edited my DNS servers I get the following;

H:\>NSLOOKUP ae-srv-01
*** Can't find server name for address 192.168.1.2: Non-existent domain
Server:  home
Address:  192.168.1.254
 
*** home can't find ae-srv-01: Non-existent domain

Open in new window

okay
"I have had to manually input my DNS servers;
192.168.1.2 (SBS)
192.168.1.254 (Router)"
you never need to set any dns servers manually.
the ONLY dns server is the SBS server, so on the sbs server itself it points to itself (192.168.1.2) as the dns, and the clients need to be on DHCP, provided by the SBS server. So the clients also point to the SBS server as their ONLY dns server.
on the SBS you need to RERUN the connect to the internet wizard and give in the ISP dns servers when you get to that part.
for an overview:
http://www.sbs-rocks.com/sbs2k3/sbs2k3-n2.htm
I re-run the wizard on the first day Suppsaws.

I know what you are saying that I shouldn't enter any DNS manually but at the time that was the only way to get to this website.

I have since re-run the wizard and also clear the dns cache on the server.

Put DNS back to automatic on here and restarted.

Everything seems fine now but I'm a little hesitant to change everyones settings at this time.
if you just follow the wizards, and if the cients are (re) joined correctly, everything should work.
That's what I did last week with this client and I had DNS issues on Friday and today..
can you post an ipconfig of that client + sbs again please?
so the CEICW wizard ran without any error? and the client was rejoined correctly using the connectcomputer method, right?
Yes to both CEICW and ConnectComputer.

MY IPCONFIG
H:\>ipconfig/all
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : CRAIG-WALKER
        Primary Dns Suffix  . . . . . . . : AEDirectMail.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : AEDirectMail.local
                                            AEDirectMail.local
 
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . : AEDirectMail.local
        Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Con
nection
        Physical Address. . . . . . . . . : 00-21-5A-76-B5-77
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.24
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.254
        DHCP Server . . . . . . . . . . . : 192.168.1.2
        DNS Servers . . . . . . . . . . . : 192.168.1.2
        Primary WINS Server . . . . . . . : 192.168.1.2
        Lease Obtained. . . . . . . . . . : 23 February 2009 09:23:14
        Lease Expires . . . . . . . . . . : 03 March 2009 09:23:14
 
H:\>

Open in new window

SBS


C:\>ipconfig/all
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : ae-srv-01
   Primary Dns Suffix  . . . . . . . : AEDirectMail.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : AEDirectMail.local
 
Ethernet adapter Server Local Area Connection:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit Server A
dapter
   Physical Address. . . . . . . . . : 00-1E-0B-DD-53-C0
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254
   DNS Servers . . . . . . . . . . . : 192.168.1.2
   Primary WINS Server . . . . . . . : 192.168.1.2
 
C:\>

Open in new window

okay, the ipconfigs look good, now let's narrow down this issue.

so you can go to the internet on the server?
can you go to the internet on the client?
can you ping google on the server?
can you ping google on the client?
can you ping 74.125.79.99 from server/client?
so you can go to the internet on the server? YES
can you go to the internet on the client? YES
can you ping google on the server? YES
can you ping google on the client? YES
can you ping 74.125.79.99 from server/client? YES

I think everything is fine now, but it was like that last week until Friday.
Just to clarify though, this does seem to have stopped my offline files original issue :)
ow, lol, I've misread then ... :)
so there are no more issues now?
Well if the DNS goes mental again then there will be issues.

At this present moment, nope, no issues.

But if what happened on Friday happens again (no dns resolution for websites) then I have issues.
Thanks for all your help suppsaws..
normaaly there shouldn't be anymore dns issues (unless you have smth manually configured in the dns settings).
But since you reran the CEICW the only two dns servers are your isp dns servers, and they should be added to the 'forwarders' tab in your server dns properties if you look at it.
btw, did you also do ALL the latest windows updates on the sbs server?
no problem, glad to help people, that is why I am here on this site :-)
Quote "But since you reran the CEICW the only two dns servers are your isp dns servers, and they should be added to the 'forwarders' tab in your server dns properties if you look at it."

I can't see them in the dnsmngmt console. Where should I be looking?
admin tools > dns
right click your server > properties > forwarders
there should be the two ISP dns servers configured in the CEICW .
http://www.sbs-rocks.com/sbs2k3/sbs2k3-n2.htm
Yes they are both there.

Thanks very much.
Ahhhhhhhhhhhhh

Just lost DNS again.

My client pinging google.com and IP.

H:\>ping google.com
Ping request could not find host google.com. Please check the name and try again
.
 
H:\>ping 74.125.67.99
 
Pinging 74.125.67.99 with 32 bytes of data:
 
Reply from 74.125.67.99: bytes=32 time=134ms TTL=234
Reply from 74.125.67.99: bytes=32 time=132ms TTL=234
Reply from 74.125.67.99: bytes=32 time=131ms TTL=234
Reply from 74.125.67.99: bytes=32 time=133ms TTL=234
 
Ping statistics for 74.125.67.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 131ms, Maximum = 134ms, Average = 132ms
 
H:\>

Open in new window

hm, I wonder if there aint smth wrong on your modem/router/firewall then? (so your gateway actually)
because on the SBS itsef iverything is fine.
SBS pings nothing;


C:\>ping google.com
Ping request could not find host google.com. Please check the name and try again
.
 
C:\>ping 74.125.79.99
 
Pinging 74.125.79.99 with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 74.125.79.99:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>ping 74.125.67.99
 
Pinging 74.125.67.99 with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 74.125.67.99:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>ping 74.125.67.100
 
Pinging 74.125.67.100 with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 74.125.67.100:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>

Open in new window

so when you ping with your pc, you don't get a reply, but do you get a reply when you ping on the server itself?
I mean a name ping, not a ip ping.

you don't lose your internet connection it seems, that there still is a dns issue, although all your dns settings are fine.
are you also sure your isp dns servers are the correct ones?
The only way for me to get on the net right now is to manually change the DNS servers to 192.168.1.2 and 192.168.1.254.

My configuration now to get on net;


H:\>ipconfig/all
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : CRAIG-WALKER
        Primary Dns Suffix  . . . . . . . : AEDirectMail.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : AEDirectMail.local
                                            AEDirectMail.local
 
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . : AEDirectMail.local
        Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Con
nection
        Physical Address. . . . . . . . . : 00-21-5A-76-B5-77
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.24
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.254
        DHCP Server . . . . . . . . . . . : 192.168.1.2
        DNS Servers . . . . . . . . . . . : 192.168.1.2
                                            192.168.1.254
        Primary WINS Server . . . . . . . : 192.168.1.2
        Lease Obtained. . . . . . . . . . : 23 February 2009 11:57:45
        Lease Expires . . . . . . . . . . : 03 March 2009 11:57:45
 
H:\>

Open in new window

ISP's DNS are correct, got them from BT themselves.

When I ping a name from my PC I get nothing, when I ping the IP I get a response.
I get nothing at all when on the SBS.
It's all just kicked back in again now....

Weird!
SBS SERVER


C:\>ping google.com
 
Pinging google.com [209.85.171.100] with 32 bytes of data
 
Reply from 209.85.171.100: bytes=32 time=190ms TTL=234
Reply from 209.85.171.100: bytes=32 time=191ms TTL=234
Reply from 209.85.171.100: bytes=32 time=193ms TTL=234
Reply from 209.85.171.100: bytes=32 time=188ms TTL=234
 
Ping statistics for 209.85.171.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 188ms, Maximum = 193ms, Average = 190ms
 
C:\>ping 74.125.79.99
 
Pinging 74.125.79.99 with 32 bytes of data:
 
Reply from 74.125.79.99: bytes=32 time=58ms TTL=236
Reply from 74.125.79.99: bytes=32 time=55ms TTL=236
Reply from 74.125.79.99: bytes=32 time=52ms TTL=236
Reply from 74.125.79.99: bytes=32 time=53ms TTL=236
 
Ping statistics for 74.125.79.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 58ms, Average = 54ms
 
C:\>ping 74.125.67.100
 
Pinging 74.125.67.100 with 32 bytes of data:
 
Reply from 74.125.67.100: bytes=32 time=135ms TTL=235
Reply from 74.125.67.100: bytes=32 time=131ms TTL=235
Reply from 74.125.67.100: bytes=32 time=133ms TTL=235
Reply from 74.125.67.100: bytes=32 time=130ms TTL=235
 
Ping statistics for 74.125.67.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 130ms, Maximum = 135ms, Average = 132ms
 
C:\>

Open in new window

hm, could be your gateway that is causing this.
since it works with 192.168.1.254 added I guess the problem could be the gateway that is not allowing the ping requests, or the dns resolving.
when the problem occurs you could do a tracert to google to see what device is stopping the traffic.
also, update the drivers of the SBS nic if that isn't already done.
Yeah everything is up to date. First thing I did from your request. Restarted at weekend.
then a tracert and a look at the gateway/router will be the first step in solving this.
Happened again :-(

I'll post various tracert's below.

My Client (Setup correctly took over 5 mins to complete the trace)
The SBS was quite fast at saying not responding
A client with manually set DNS was instant
MY CLIENT (SETUP CORRECT, DHCP, CONNECT COMPUTER)

H:\>tracert google.com
Unable to resolve target system name google.com.
 
H:\>tracert 74.125.67.100
 
Tracing route to 74.125.67.100 over a maximum of 30 hops
 
  1     1 ms    <1 ms     1 ms  192.168.1.254
  2    35 ms    37 ms    37 ms  217.47.30.200
  3    38 ms    39 ms    35 ms  217.47.30.162
  4    40 ms    37 ms    39 ms  217.47.30.234
  5   118 ms    66 ms    39 ms  217.47.219.82
  6    38 ms    39 ms    39 ms  217.41.168.25
  7    37 ms    37 ms    39 ms  217.41.168.66
  8    43 ms    39 ms    39 ms  217.41.168.78
  9    40 ms    41 ms    39 ms  217.41.168.46
 10    43 ms    37 ms    37 ms  217.47.70.114
 11    37 ms    39 ms    39 ms  194.72.17.113
 12    42 ms    41 ms    43 ms  195.99.125.189
 13    48 ms    45 ms    47 ms  195.99.125.78
 14    42 ms    41 ms    41 ms  209.85.252.76
 15   108 ms   129 ms   130 ms  216.239.43.192
 16   125 ms   118 ms   114 ms  216.239.43.113
 17   106 ms   112 ms   110 ms  209.85.255.138
 18   125 ms   135 ms   131 ms  66.249.94.235
 19   134 ms   136 ms   116 ms  66.249.95.127
 20   141 ms   114 ms   114 ms  72.14.238.233
 21   130 ms   130 ms   132 ms  72.14.238.138
 22   131 ms   132 ms   130 ms  74.125.67.100
 
Trace complete.
 
H:\>

Open in new window

SBS


C:\>tracert google.com
Unable to resolve target system name google.com.
 
C:\>tracert 74.125.67.100
 
Tracing route to 74.125.67.100 over a maximum of 30 hops
 
  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
 
Trace complete.
 
C:\>

Open in new window

OTHER CLIENT


H:\>ping google.com
 
Pinging google.com [74.125.67.100] with 32 bytes of data:
 
Reply from 74.125.67.100: bytes=32 time=136ms TTL=235
Reply from 74.125.67.100: bytes=32 time=133ms TTL=235
Reply from 74.125.67.100: bytes=32 time=132ms TTL=235
Reply from 74.125.67.100: bytes=32 time=140ms TTL=235
 
Ping statistics for 74.125.67.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 132ms, Maximum = 140ms, Average = 135ms
 
H:\>tracert google.com
 
Tracing route to google.com [74.125.67.100]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms     1 ms  home [192.168.1.254]
  2    38 ms    35 ms    37 ms  btdhg512-hg1.ealing.broadband.bt.net [217.47.30.
200]
  3    37 ms    37 ms    37 ms  217.47.30.130
  4    40 ms    37 ms    39 ms  217.47.30.238
  5    43 ms    35 ms    37 ms  217.47.219.82
  6    40 ms    39 ms    39 ms  217.41.168.25
  7    39 ms    41 ms    45 ms  217.41.168.66
  8    38 ms    43 ms    43 ms  217.41.168.78
  9    39 ms    37 ms    39 ms  217.41.168.46
 10    41 ms    37 ms    37 ms  217.47.70.114
 11    42 ms    41 ms    39 ms  core3-pos0-8-0-0.ealing.ukcore.bt.net [194.72.17
.113]
 12    43 ms    44 ms    41 ms  core1-pos14-0.telehouse.ukcore.bt.net [195.99.12
5.189]
 13    43 ms    43 ms    41 ms  195.99.125.78
 14    41 ms    41 ms    39 ms  209.85.252.76
 15   124 ms   127 ms   112 ms  216.239.43.192
 16   118 ms   149 ms   132 ms  209.85.248.216
 17   163 ms   125 ms   120 ms  72.14.238.235
 18   115 ms   114 ms   112 ms  66.249.94.235
 19   115 ms   116 ms   133 ms  209.85.254.247
 20   129 ms   114 ms   116 ms  72.14.238.233
 21   158 ms   130 ms   131 ms  72.14.238.138
 22   131 ms   133 ms   130 ms  209.85.254.247
 23   131 ms   128 ms   130 ms  gw-in-f100.google.com [74.125.67.100]
 
Trace complete.
 
H:\>

Open in new window

hmmmmm, since you can't even ping or trace an IP on the server I guess there is smth wrong with your NIC on the sbs server.
You can do all this on your client since it goes directly to your gateway and NOT via the sbs, so the problem is the SBS server itself.
First update the NIC drivers on the SBS, and if that is not helping, try adding a second nic.