SBS 2008 Internet

Dell Poweredge t310 tower server - custo...
April 28, 2011 at 01:51:04
Specs: SBS 2008, Xeon
I need assistance in resolving an internet issue for a small domain that is setup with SBS 2008 server setup and 10 Workstations. Throughout the day the workstations will lose their internet connection. All the computers stay connected on the LAN ok, even when the internet connection drops. The ISP tested their equipment by plugging a computer into their router with a static IP and the connection never has an issue. I think it may be a DNS configuration issue as the server was never setup properly by the person who installed it. I am not familiar with troubleshooting this and so far checked the Event Logs on the server and workstation - nothing specific as to why this is occurring. Any ideas are appreciated. Thanks.

See More: SBS 2008 Internet

Report •


#1
April 28, 2011 at 10:20:34
post the results of a ipconfig /all from the server and a workstation for review.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
April 28, 2011 at 17:13:00
Here is the info (SBS 2008 and XP IPConfig /ALL)

SBS 2008 Server IPConfig /All

Windows IP Configuration

Host Name . . . . . . . . . . . . : SBS2008SRV
Primary Dns Suffix . . . . . . . : SBSDomain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SBSDomain.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
Physical Address. . . . . . . . . : 00-26-B9-34-1A-A7
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d91:1c76:c38:1872%11(Preferred)
Link-local IPv6 Address . . . . . : fe80::1da0:58ef:d06f:5064%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : fe80::1da0:58ef:d06f:5064%11
192.168.0.2
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-26-B9-34-1A-A6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{BBE35F91-C688-4CD0-8426-E1781501B5FD}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


============================================================


Windows XP Pro (SP3) IPConfig /All

Host Name . . . . . . . . . . . . : XP1

Primary Dns Suffix . . . . . . . : SBSDomain.local

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : SBSDomain.local

SBSDomain.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : SBSDomain.local

Description . . . . . . . . . . . : Intel(R) 82562V 10/100 Network Connection

Physical Address. . . . . . . . . : 00-16-76-C2-C0-A3

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.20

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.2

DNS Servers . . . . . . . . . . . : 192.168.0.2

Lease Obtained. . . . . . . . . . : Monday, April 25, 2011 3:21:23 AM

Lease Expires . . . . . . . . . . : Tuesday, May 03, 2011 3:21:23 AM


Report •

#3
April 29, 2011 at 08:09:46
everything looks good except for this anomoly.

Link-local IPv6 Address . . . . . : fe80::d91:1c76:c38:1872%11(Preferred)
Link-local IPv6 Address . . . . . : fe80::1da0:58ef:d06f:5064%11(Preferred)

I have never see ipv6 installed twice on a interface. Might want to look into that though this should have nothing to do with your outages.

The next test has to happen during a outage.

from a workstation do a nslookup of the local server name and then do a nslookup of yahoo.com. Then do a tracert to 98.137,149.56 [yahoo.com]. Post the results for review.

What we are trying to do if figure out is the outage is hardware or software based. Right now we are looking at software config concerning internet access. The question is when you have this outage where is it broken. Is it name resolution, which the dns server is responsible for or is it actually the isp

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
April 29, 2011 at 08:27:38
Thanks for following up. It looks like it isn't the ISP. If I connect one of the computers that is having an internet problem on the LAN directly into the ISP router (with Static IP address), it never loses internet connectivity.
There are 5 computers on the LAN (Four XP Pro and One Vista).
The Vista computer never has a problem losing internet access.
The XP computers will stay connected for 5 minutes and then they drop off for about 30 minutes and then the internet access will come back (without having to reboot anything). I will post the results of the NSLOOKUP and Tracert later on today.

Report •

#5
April 29, 2011 at 17:47:33
Below are the results, I ran NSLOOKUP to the Server and Yahoo.com and
Tracert to ip of yahoo.com after the computer started getting request timeout.
Below are the results
:
C:\>nslookup fileserver
Server: www.domain.com
Address: 192.168.0.2

Name: fileserver.domain.local
Address: 192.168.0.2

C:\>nslookup yahoo.com
Server: www.domain.com
Address: 192.168.0.2

Non-authoritative answer:
Name: yahoo.com
Addresses: 209.191.122.70, 67.195.160.76, 69.147.125.65, 72.30.2.43
98.137.149.56

c:\>tracert yahoo.com

Tracing route to ir1.fp.vip.sp2.yahoo.com [98.137.149.56]

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.


Report •


Ask Question