Hey! That's good that you found and fixed the DNS issue.
About the slow transfers... I don't have too much advice there, but... I
have seen on numerous occasions where having a NIC hardcoded to 100/full has
caused very slow performance due to repeated send/receive errors on packets.
I'd take a look at the NICs. If they are set to hardcoded 100/full, I'd
change it to "auto-negotiate" on each and see if that makes any difference.
I've also heard that turning off SMB signing can sometimes help with speed
issues. But I've never done that and don't know much about it.
-Frank
"Rob" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed). ..
> This was indeed, I'm sorry to say, the problem. I knew it was going to be
> something relatively simple that I was missing - something I should know
> better than - but I couldn't turn it up.
>
> Some file transfer stuff remains a bit slow, but all file resolves are
> fast now (odd though, since they were slow even if I used an IP address
> before). The slow stuff is things not copying as fast as it should, but I
> have a bit more testing to do on that - even that is clearly moving at a
> much faster pace than it was (though at least 10-20x or more slower than I
> would expect).
>
> Thanks for the help!
>
>
> "Frankster" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ...
>> To this I would say... make sure your Windows Server is running the only
>> DNS server that is available to the clients (same goes for DHCP if you're
>> using it). And... make sure that only the Windows DNS server IP is in the
>> client tcp/ip config for DNS server. Do not place the ISP provided DNS
>> server into the cleints config as primary OR secondary.
>>
>> Since you say... "it will often refuse to resolve", that tells me the
>> issue is/seems intermittent. One classic cause of seemingly intermittent
>> DNS resolution is that the clients have been wrongly configured with the
>> ISP DNS IP rather than with the internal DNS IP only.
>>
>> -Frank
>>
>> "Rob" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed). ..
>>> It's worth noting that it also will often refuse to resolve the names of
>>> other systems in the domain. In short, it's often like the other
>>> computer isn't a member of the doman at all, even though it is.
>>>
>>>
>>> "Rob" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed). ..
>>>>I have an issue where any of several boxes on a Win2003 server domain
>>>>(SP2 on the domain server) have several connection issues with each
>>>>other.
>>>>
>>>> 1. Despite being able to see the domain server well enough to log into
>>>> the domain, any connection to a different system on the network
>>>> requires authentication into that local box using a login local to that
>>>> box (even if logged into the domain as a domain admin, and the domain
>>>> admin is a administrator on all domain boxes).
>>>> 2. Prior to the demand for local log in, the explorer process that you
>>>> navigated to the remote box with will hang for several minutes prior to
>>>> showing the authentication dialog.
>>>> 3. Even after authenticated, any file resolutions (for example,
>>>> navigating to a file in explorer) will take as long as a full minute or
>>>> more to resolve to the file. For example, I navigate to a new
>>>> directory, that takes a while. Now, I select a new file in that
>>>> directory (a file already showing in the explorer window), and that
>>>> takes a while.
>>>> 4. If a copy is initiated between boxes on the network, the copy will
>>>> happen at an unbelievably slow rate, and will often time out as a "file
>>>> unavailable" error.
>>>>
>>>> Some facts on the network:
>>>> Server is Win2003 SP2 with most security patches since SP2's release.
>>>> The domain install is pretty much the 2003 domain default installation
>>>> The network is 100Mb network
>>>> All boxes are behind the firewall
>>>> Connections outside the network (to the internet) happen at normal
>>>> speeds
>>>> Windows Firewall is *not* enabled on any box in the domain
>>>> As near as I can tell, all boxes in the network are affected no matter
>>>> what box they are conntecting two.
>>>>
>>>> Any idea what is at issue here? I have occassionally seen issues on
>>>> other networks where the remote box seems to partially lose resolution
>>>> authenticating on the network other than initial login, but I've never
>>>> seen the speed issues before.
>>>>
>>>> TIA
>>>>
>>>
>>>
>>
>>
>
>
|
Similar Threads
Linear Mode
