From: Russ SBITS.Biz [SBS-MVP] on 17 May 2010 00:36 Frankster Double check what Cliff said about TOE Russ -- Russell Grover - SBITS.Biz [SBS-MVP] MCP, MCPS, MCNPS, SBSC Small Business Server/Computer Support - www.SBITS.Biz BPOS - Microsoft Online Services - www.Microsoft-Online-Services.com "Frankster" <frank(a)SPAM2TRASH.com> wrote in message news:3LGdnXa2D8cxEm3WnZ2dnUVZ_vKdnZ2d(a)giganews.com... >> Normally I'd agree, but if pinging an IP works (the OP used 8.8.8.8 as an >> example) and then stops, that is not DNS related. This is the SBS server >> itself failing to access or use the default gateway properly and is >> unrelated to DNS. > > Could be. After re-reading his post, I find it hard to tell just when > "internet connectivity" started/stopped working on the server or the > client. > > -Frank
From: Joe on 17 May 2010 04:34 On 16/05/10 22:07, AlexT. wrote: > > I will start to do some packet capture tomorrow but in the meantime > any idea / suggestion most welcome. > Plenty so far, but check for a default gateway on the SBS with ipconfig. SBS2008 is notorious for losing the default gateway after a reboot, and Google will find various suggestions to fix it. Two common ones: -if the SBS has ever given itself a different IP address than it has now, there may be a reference to that network in its routing table. -check the gateway entry for TCP/IP, if there is a blank line before the actual IP address, remove that. -- Joe
From: Ace Fekay [MVP - Directory Services, MCT] on 17 May 2010 11:50 On Sun, 16 May 2010 21:36:15 -0700, "Russ SBITS.Biz [SBS-MVP]" <russ(a)REMOVETHIS.sbits.biz> wrote: >Frankster >Double check what Cliff said about TOE >Russ To add to all the responses, I would also look at DNS properties, Interface tab and make sure the outer interface is not set to listen on. As for the DSL setup, I've seen where a PPPoE connection that falls asleep after inactivity, and the outer interface is directly connected to such a router/firewall/modem, will cause DNS to stop, and a DNS service restart will kick it back on again. It also could be an EDNS0 issue. I don't know what model the Zywall is, but EDNS0 is a common issue when things appear 'intermittent' or 'selective' resolution works. I would suggest to also look into the Zywall docs to see if it supports EDNS0 issue. One way to confirm if it is an issue, is to configure a Forwarder to 4.2.2.3. If all works all the time, then I would look at that as a red flag saying it is lack of the Zywall supporting EDNS0. Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution. Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
From: AlexT. on 18 May 2010 10:39 > 1) Check and download the latest NIC drivers. Don't rely on the out-of-box > 2008 drivers for NICs. right on the money - updating to the lattest NIC drivers "magically" cured my problem !! good catch - thanks --alexT
First
|
Prev
|
Pages: 1 2 Prev: SBS2008 Report E-mail Delay Next: Mobile sync over the air - error code 0x80072ee7 |