New Installation, Very Slow Performance

December 3, 2010 at 19:07:42
Specs: Windows Server 2008
Setting up a small home network and just installed Server 2008 on a Dell GX280, P4 2.8 Ghz, 3 GB RAM. I have 2 harddrives, both 2 TB WD20EARS, relatively new and newly formatted. I know this isn't the typical hardware for a server, but I'm basically just looking for it to manage a domain, do my DNS and DHCP, and act as a file server.

Working directly on the server goes ok, but trying to copy to/from it over the network is extremely slow. (All my clients are running windows 7) I'm only getting transfer rates of 1-2 MB/s. I can download files from the internet faster, in some cases.

I'm not quite sure what to start looking at to troubleshoot. I realize with this hardware I'm not going to get the best server performance, but certainly better than this. Any ideas on where to start to look?


See More: New Installation, Very Slow Performance

Report •


#1
December 4, 2010 at 11:14:18
What are the workstations pointing to for dns? This servers ip or the gateway ip?

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#2
December 4, 2010 at 12:00:40
The workstation points to the server as the DNS server (10.8.10.10) and the router as the gateway (10.8.10.1).

Report •

#3
December 5, 2010 at 08:30:07
Great. Lets test it. Do a nslookup yahoo.com from a workstation. Then to a tracert yahoo.com and post the results of both.

Answers are only as good as the information you provide.
How to properly post a question:


Report •

Related Solutions

#4
December 5, 2010 at 10:56:54
C:\Users\jesseplace>nslookup yahoo.com
Server: UnKnown
Address: 10.8.10.10

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

------------------------------------------------

C:\Users\jesseplace>tracert yahoo.com

Tracing route to yahoo.com [209.191.122.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.8.10.1
2 <1 ms 1 ms 1 ms 192.168.1.1
3 6 ms 4 ms 5 ms L100.NWRKNJ-VFTTP-139.verizon-gni.net [74.102.58
.1]
4 6 ms 6 ms 7 ms G14-0-1-1439.NWRKNJ-LCR-04.verizon-gni.net [130.
81.146.72]
5 7 ms 7 ms 7 ms so-6-1-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
29.194]
6 10 ms 8 ms 7 ms so-3-3-0-0.NY5030-BB-RTR2.verizon-gni.net [130.8
1.17.14]
7 17 ms 16 ms 19 ms so-9-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.1
7.10]
8 17 ms 17 ms 17 ms so-7-0-0-0.ASH-PEER-RTR1-re1.verizon-gni.net [13
0.81.10.94]
9 16 ms 16 ms 16 ms 130.81.15.50
10 18 ms 16 ms 17 ms ae-6.pat1.dcp.yahoo.com [216.115.102.174]
11 60 ms 44 ms 58 ms as-4.pat1.da3.yahoo.com [216.115.96.111]
12 65 ms 64 ms 60 ms ae-2-d120.msr1.mud.yahoo.com [216.115.104.89]
13 59 ms 61 ms 59 ms te-6-2.fab1-a-gdc.mud.yahoo.com [209.191.78.145]

14 61 ms 63 ms 65 ms te-8-2.fab1-a-gdc.mud.yahoo.com [209.191.78.149]

15 59 ms 66 ms 60 ms ir1.fp.vip.mud.yahoo.com [209.191.122.70]

Trace complete.


Report •

#5
December 6, 2010 at 10:58:35
Server: UnKnown

That's not good. Did you add your ISP's dns server ips into the forwarders [not to be confused with forward lookup zone] in DNS server?

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#6
December 6, 2010 at 17:01:55
What doesn't look good. Yes, I have two forwarders defined in the DNS settings that are from the ISP.

Report •

#7
December 7, 2010 at 07:13:07
C:\Users\jesseplace>nslookup yahoo.com
Server: UnKnown <---- this is what is wrong
Address: 10.8.10.10

Do a nslookup of your server name. Server listed as unknown as above?

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#8
December 7, 2010 at 14:51:20
C:\Users\jesseplace>nslookup JPP-SERVER08
Server: UnKnown
Address: 10.8.10.10

Name: JPP-SERVER08.JPP.local
Address: 10.8.10.10


Report •

#9
December 7, 2010 at 15:48:55
The "unknown" should come back as
yourdnsserver.yourdomainname.ext

This indicates you are missing entries in your dns server.

You should have
(same as parent folder) name server (ns) servername.domainname.ext

ext is local/com/org whatever you are using.

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#10
December 7, 2010 at 16:00:53
Ok, I'm seeing three (same as parent) entries in the forward lookup zone for my domain...

(same as parent folder) Start of Authority (SOA) [35] jpp-server08.jpp.local., hostmaster.jpp.local. static

(same as parent folder) Name Server (NS) JPP-SERVER08.JPP.local. static

(same as parent folder) Host (A) 10.8.10.10


Report •

#11
December 8, 2010 at 08:12:27
do you have?

JPP-SERVER08 Host(A) 10.8.10.10

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#12
December 9, 2010 at 02:40:37
Yes, there is an A record for both the server and client.

Report •

#13
December 9, 2010 at 06:49:58
If you do a ipconfig /all on the server is its dns entry pointing to itself via its ip address not 127.0.0.1?

If so than I am out of clues. Your name server can't resolve itself. Seems the rest of your name resolution is working so this should not be your source of network slowness.

Please post a ping between workstation and server. thanks

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#14
December 9, 2010 at 18:31:45
ipconfig /all on server...

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-12-3F-8C-15-73
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::14e9:206b:1082:5e05%10(Preferred)
IPv4 Address. . . . . . . . . . . : 10.8.10.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.8.10.1
DNS Servers . . . . . . . . . . . : ::1
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{2F24B210-69B6-44B7-A622-A9F3D3E3F
323}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


------------------------------

C:\Users\jesseplace>ping JPP-SERVER08

Pinging JPP-SERVER08 [fe80::14e9:206b:1082:5e05%13] with 32 bytes of data:
Reply from fe80::14e9:206b:1082:5e05%13: time<1ms
Reply from fe80::14e9:206b:1082:5e05%13: time<1ms
Reply from fe80::14e9:206b:1082:5e05%13: time<1ms
Reply from fe80::14e9:206b:1082:5e05%13: time<1ms

Ping statistics for fe80::14e9:206b:1082:5e05%13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Report •

#15
December 10, 2010 at 07:42:17
theres the problem

DNS Servers . . . . . . . . . . . : ::1
127.0.0.1

get rid of the "1'" [invalid entry] and the 127.0.0.1 and only have 10.8.10.10 for dns

nslookup should come back with the server name instead of unknown now.

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#16
December 10, 2010 at 16:17:25
ok, the bad DNS address was in the IPv6 properties, not sure how it got there...

I made the changes but the server still comes back as unknown doing nslookup from the client...

C:\Users\jesseplace>nslookup JPP-SERVER08
Server: UnKnown
Address: 10.8.10.10

Name: JPP-SERVER08.JPP.local
Address: 10.8.10.10


-------------------------------------
ipconfig on server
---------------------------------------

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-12-3F-8C-15-73
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::14e9:206b:1082:5e05%10(Preferred)
IPv4 Address. . . . . . . . . . . : 10.8.10.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.8.10.1
DNS Servers . . . . . . . . . . . : 10.8.10.10
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{2F24B210-69B6-44B7-A622-A9F3D3E3F
323}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Report •


Ask Question