I have a Win XP SP2 PC on a domain. It's up to date for any updates. After
the PC boots up the user is unable to access a shortcut on the desktop with a
link such as \\server\shared\tryme.exe . It takes around 5 minutes of trying
before the user can use the app. The PC has a static IP address with the
correct settings (even with a dynamic address, same problem). The power
management for the NIC is off. It's connected to a switch with 2 other PCs.
The other 2 PCs have no issuesand the cable for the PC with the problem has
changed. Ideas?
Gis Bun wrote:
> I have a Win XP SP2 PC on a domain. It's up to date for any updates. After
> the PC boots up the user is unable to access a shortcut on the desktop with a
> link such as \\server\shared\tryme.exe . It takes around 5 minutes of trying
> before the user can use the app. The PC has a static IP address with the
> correct settings (even with a dynamic address, same problem). The power
> management for the NIC is off. It's connected to a switch with 2 other PCs.
> The other 2 PCs have no issuesand the cable for the PC with the problem has
> changed. Ideas?
You say the settings are correct, but the symptoms you describe normally
occur when DNS is wrong. Please recheck the DNS settings; the
workstation should only be looking to the server for DNS.
> Gis Bun wrote:
> > I have a Win XP SP2 PC on a domain. It's up to date for any updates. After
> > the PC boots up the user is unable to access a shortcut on the desktop with a
> > link such as \\server\shared\tryme.exe . It takes around 5 minutes of trying
> > before the user can use the app. The PC has a static IP address with the
> > correct settings (even with a dynamic address, same problem). The power
> > management for the NIC is off. It's connected to a switch with 2 other PCs.
> > The other 2 PCs have no issuesand the cable for the PC with the problem has
> > changed. Ideas?
>
> You say the settings are correct, but the symptoms you describe normally
> occur when DNS is wrong. Please recheck the DNS settings; the
> workstation should only be looking to the server for DNS.
>
>
> Malke
>
The DNS settings are fine. We have 100+ PCs using reserved DHCP addresses
including this PC. Yet this is the only PC with the issue.
Gis Bun wrote:
>
> "Malke" wrote:
>
>> Gis Bun wrote:
>>> I have a Win XP SP2 PC on a domain. It's up to date for any updates. After
>>> the PC boots up the user is unable to access a shortcut on the desktop with a
>>> link such as \\server\shared\tryme.exe . It takes around 5 minutes of trying
>>> before the user can use the app. The PC has a static IP address with the
>>> correct settings (even with a dynamic address, same problem). The power
>>> management for the NIC is off. It's connected to a switch with 2 other PCs.
>>> The other 2 PCs have no issuesand the cable for the PC with the problem has
>>> changed. Ideas?
>> You say the settings are correct, but the symptoms you describe normally
>> occur when DNS is wrong. Please recheck the DNS settings; the
>> workstation should only be looking to the server for DNS.
>>
>>
>> Malke
>>
>
> The DNS settings are fine. We have 100+ PCs using reserved DHCP addresses
> including this PC. Yet this is the only PC with the issue.
Bad hardware perhaps, some third-party security program, iffy wiring to
whatever connects to your network, failing NIC, marginal switch. Sorry,
but there's no way to tell without examining the machine first-hand.
> Gis Bun wrote:
> >
> > "Malke" wrote:
> >
> >> Gis Bun wrote:
> >>> I have a Win XP SP2 PC on a domain. It's up to date for any updates. After
> >>> the PC boots up the user is unable to access a shortcut on the desktop with a
> >>> link such as \\server\shared\tryme.exe . It takes around 5 minutes of trying
> >>> before the user can use the app. The PC has a static IP address with the
> >>> correct settings (even with a dynamic address, same problem). The power
> >>> management for the NIC is off. It's connected to a switch with 2 other PCs.
> >>> The other 2 PCs have no issuesand the cable for the PC with the problem has
> >>> changed. Ideas?
> >> You say the settings are correct, but the symptoms you describe normally
> >> occur when DNS is wrong. Please recheck the DNS settings; the
> >> workstation should only be looking to the server for DNS.
> >>
> >>
> >> Malke
> >>
> >
> > The DNS settings are fine. We have 100+ PCs using reserved DHCP addresses
> > including this PC. Yet this is the only PC with the issue.
>
> Bad hardware perhaps, some third-party security program, iffy wiring to
> whatever connects to your network, failing NIC, marginal switch. Sorry,
> but there's no way to tell without examining the machine first-hand.
>
> Good luck and EOT for me.
>
>
> Malke
>
Well, the cable was changed, The cable was also put in another port on the
switch. So I can rule them out. No third party security software. Just our
standard AV.
I'll probably just disable the NIC and pop in another one then.
Win XP SP2 PC with slow connection... 
Linear Mode
