RE: Poor network performance
From: Jeff Strubberg (JeffStrubberg_at_discussions.microsoft.com)
Date: 08/13/04
- Next message: bu: "WinNT domain and Win2k Domain on same physical backbone"
- Previous message: Charles: "Copy & Paste in Terminal Server"
- In reply to: MartinP: "RE: Poor network performance"
- Next in thread: anonymous_at_discussions.microsoft.com: "Poor network performance FIXED"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Aug 2004 07:33:03 -0700
Mmmm,
Have you contacted the software manufacturer yet? It would be interesting
to find out what method they are using for file access. Could be FTP, mapped
drive, direct DNS lookup, etc. You may have to badger them enoug to talk to
a developer to get any kind of a meaningful answer, though.
"MartinP" wrote:
> OK, I spent a couple of hours on this last night, fixed a
> problem or two but still didn't clear it up.
>
> ipconfig /all from the DC is as follows:
> Windows IP Configuration
> Host name D1600SC
> Primary DNS Suffix SeagraveNJ.local
> Node Type Hybrid
> IP Routing Enabled No
> WINS Proxy Enabled No
> DNS Suffix Search List SeagraveNJ.local
>
> Ethernet adapter Local Area Connection
> Connection-specific DNS Suffix {no entry}
> Description Intel(R) PRO/1000 MT Network Connection
> Physical address 00-C0-9F-3F-0E-CA
> DHCP Enabled No
> IP Address 192.168.1.10
> Subnet Mask 255.255.255.0
> Default Gateway 192.168.1.5
> DNS Servers 192.168.1.10
> Primary WINS server 192.168.1.10
>
> I tried doing NSLOOKUP from the server and a client but
> this is the result
> nslookup d1600sc
> ***Can't find server name for address 192.168.1.10: Non-
> existent domain
> ***Default servers are not available
> Server: UnKnown
> Address: 192.168.1.10
>
> Name: d1600sc.SeagraveNJ.local
> Address: 192.168.1.10
>
> The DNS server was already pointing to itself for DNS.
> Some of the clients still had a WINS address which was
> from the old network [changed from 172.0.0.x to
> 192.168.1.x with new server] so I deleted manual WINS
> entry in TCP/IP properties. Also set up WINS on server.
> Ran NETDIAG, which returned all PASSES.
>
> It looks like the file access and transfer times are
> better, but the response time in the manufacturing
> software is still horrendous.
>
> Martin
> >-----Original Message-----
> >Jeff,
> >I'll check that tonight. I only hope it's that simple, but
> >that is the kind of issue I am seeing.
> >
> >Martin
> >>-----Original Message-----
> >>Martin,
> >>
> >>You should also confirm that the DNS addresses for the
> ISP
> >are not enterd in
> >>the TCIP properties window on the client. In a domain
> >environment, the
> >>client should have teh local server as it's DNS. The
> >server should have
> >>forward lookups for the ISP DNS.
> >>
> >>
> >>Otherwise, every DNS request ends up routed out to the
> big
> >world-wide cloud
> >>rather than being resolved locally. I just stumbled
> >across this problem
> >>yesterday after reading a post here on Technet. I
> changed
> >the setting on
> >>four of my cleint machines that had been a problem and
> saw
> >login and file
> >>access timesw across the network from those machines drop
> >from three to four
> >>minutes to less than two seconds.
> >
> >.
> >
>
- Next message: bu: "WinNT domain and Win2k Domain on same physical backbone"
- Previous message: Charles: "Copy & Paste in Terminal Server"
- In reply to: MartinP: "RE: Poor network performance"
- Next in thread: anonymous_at_discussions.microsoft.com: "Poor network performance FIXED"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
