TCP very Slow

  • Thread starter Thread starter Yor Suiris
  • Start date Start date
Y

Yor Suiris

I have one 2000 Pro machine that runs very fast and nice with only NetBuie.
But add TCP\IP and it slows to a snails pace. It will not run the logon
scripts (Kix) to map drives and opening the Citrix client takes a dogs age
to happen. We have other 2000 and XP and NT and 9Xs that all do just fine.
We use DHCP so ALL have the same configuration, same DNS, same WINS, same
everything.
Anyone have a suggestion as to why? Or better yet, a Solution?
 
strange, ok well pls do this do a ipconfig /release
then /renew please check to see if that win2k pro client
keeps getting same ip back? if it does maybe its bad ip in
which case reserve the bad ip in dhcp to a false MAC and
name this resrvation as bad ip, then next time u reboot
the lcient in question should pick up diff ip as the bad
ip will be looking constanlty for the phantom mac
 
I already checked all that. Sorry I should have mentioned. I tried asigning
a static IP and manually enter all the data and no change. An opconfig looks
like all the rest except for local info. Address and mask and DNS and WINS

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : C_Name
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid

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

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

DNS Suffix Search List. . . . . . : Our.Domain.com

Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . : Our.Domain.com
Description . . . . . . . . . . . : OvisLink LFE-8139ATX Fast Ethernet
Adapter #2
Physical Address. . . . . . . . . : 00-4F-4E-05-D5-DB

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.0.1.154

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

Default Gateway . . . . . . . . . : 10.0.1.1

DHCP Server . . . . . . . . . . . : 10.0.1.85

DNS Servers . . . . . . . . . . . : 10.0.1.85
207.164.4.126
Primary WINS Server . . . . . . . : 10.0.1.85

Secondary WINS Server . . . . . . : 10.0.1.80

Lease Obtained. . . . . . . . . . : October 3, 2003 7:51:16 AM

Lease Expires . . . . . . . . . . : October 4, 2003 8:52:16 AM
 
Is this the ipconfig from a workstation?
There shouldn't be an external DNS in it. It should only point to your
server-IP (the 10.0.1.85 ?)
Does your server have 1 nic? And is that gateway set to 10.0.1.1?
Where does the secondary WINS-server come from?
Do you have options 003, 006, 015, 044 and 046 set in DHCP-server?

Marina
 
Yes I have 003, 006, 015, 044, & 046 all setup and have been for years. 20
other machines use the same DHCP settings and they work just fine.
And the Outside DNS IP is Our DNS server and is configured for our system.
Getting on the Web is not the question so why the concern about my gateway?
10.0.1.1 is a firewall. All our servers have one NIC.
And the secondary WINS is sitting right next to the primary and the two talk
to each other very nicely, so what do you mean by "Where does the secondary
WINS-server come from?"

Again 20 other machines work FINE. And this machine did too until about a
week ago. The problem is not with WINS, DNS or DHCP. Just this one Win2K pro
and its use of the TCP/IP protocol.
 
Check that troubled machine for spyware, run a virusscan, check the
harddisk.

Marina
 
Back
Top