Networking problem (WinXP)

Topic

New Reply

Hi!
I’ve got a WinXP machine that’s playing games with me. I’m running an NT4 domain and did not have any problems with this machine until I moved it to a cable drop that’s 275ft from the server. When logging on this message appears:
Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.

DETAIL – The network path was not found.

This message also appears as a 1521 event in the event viewer. I ran XP’s networking diagnostics and the machine fails the dns server search order on the drop 275 ft from the server but passes when connected to a drop closer. Is there a timeout setting that I can increase?? I’m wondering if the NTPDC is not answering the dns request fast enough????

Thanks for any help!
Kris

Reply | Quote

Replies

Has the 275 ft cable been tested to be ok?

DaveA I am so far behind, I think I am First
Genealogy....confusing the dead and annoying the living

Reply | Quote

Yep, there’s an NT4 Wkst box running just fine from it now.

Reply | Quote

Kris,
Don’t know of any timeout settings. I think the cable length might be just on the fringe of being too long. Hence, the fact that it fails in one mode but passes in another. Any length of cable will exhibit loss and signal delay of varying amounts. What type of cable is it? CAT5 or CAT5E (enhanced)? Guage?
Can it be shortened at all? How is it terminated? Can you temporarily move it closer to the server on a short cable, to try it that way?
The fact that you said it worked OK until you moved it seems to be the key here.
Bob

Reply | Quote

No, the cable can’t be shortened or relocated. It’s unshielded CAT 5 terminated to RJ45 (est. age 4+ yrs). I’m going to try another XP box on this same drop over the weekend and see what results. I did try a Win98 machine that also worked just fine. Puzzling…

Thanks!
Kris

Reply | Quote

What I had in mind was to use just a short piece of cable, like a jumper with RJ45’s on it to plug in, in place of the long loop. Then plug in the box there and see if that works.
Bob

Reply | Quote

Hi, Until recently I thought that if you took an ethernet product from one manufacturer and connected it to the LAN, it would work with any and all ethenet devices on the LAN. Not so. I have found that some NICs will not interwork with others, so a suggestion is to try a NIC in your machine from another manufacturer.

As a matter of interest, what NICs are you using? We have ‘standardised’ on 3com and intel with no more problems. Some of the cheapest give you what you pay for.

Doug

Reply | Quote

I do agree that not all work with each other!

This XP machine is a Dell w/an integrated NIC on the mobo. I did try another XP box that did not have any problems logging on to the network so I know its this particular machine. I’ve since contacted Dell about a replacement.

Reply | Quote