General discussion


Moving XP client to different office

By LabRaT ·
I have a system running Windows XP Pro. It was configured at the main office but has been sent to a branch office.

Main office info:
IP Addy was
Sub-net was
Gateway was

Branch office info:
IP Addy is
Sub-net is
Gateway is

I have always configured the workstations at the main office, changed the IP parameters, and shipped it to the branch office. But these new XP Pro systems got to the branch and will not connect. Actually, the network connection status is "Connected" but it shows zero packets received (many packets sent) and it cannot PING the Gateway or any other valid address on that network.

I brought the systems back to the main office, changed the IP parameters back to those correct for this office, and the system logs into the network fine.

Sent them back to the branch office but still no go. I removed NIC from Hardware Mgr, deleted the user accts, and tried to rebuild the network protocols and user accts--No Go! It looks like it is sending packets but not receiving any. Sounds like there is some security parameters screwing things up. (?)

Previous workstations ran Windows 2000 Pro and just changing the IP parameters worked fine for them. Why am I having problems with XP Pro?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by paul.n In reply to Moving XP client to diffe ...

swap the NIC cards from another PC that works if poss.
Check the domain and workgroup settings.
do an ipconfig to check that there is address there
Let me know how you fare

Collapse -

by LabRaT In reply to

NIC checks OK. domain is correct. Ipconfig shows exactly what should be there. Thanks for the suggestions.

Collapse -

by SimY In reply to Moving XP client to diffe ...

If it connects to the network at the main office, then the NIC should be fine. If you are running XP SP2, try disabling the firewall temporarily to see if it will connect. Also, you can try to connect it to a known working network point in the branch office.

Hope this helps

Collapse -

by LabRaT In reply to

It has all current updates from the Microsoft website. The firewall is off. The new system was tried in 2 offices and in the "data closet" directly to the hub with a known-good 7ft patch cable. Thanks for the suggestions.

The new system has a network status as "Connected" so it seems it connects to something (?) but it will not ping any addresses in the branch office. The connection status shows packets are being sent but zero are received. Older systems at the branch can ping each other. The new system will ping its own NIC.

When I took the system back to the main office, all I did was change the IP protocol parameters and it immediately connects and logs in. It even "found" the old user acct settings that I thought I had deleted and rebuilt.

Collapse -

by LabRaT In reply to Moving XP client to diffe ...

**Note: When I explorer the network from the branch office, it shows a domain (correct name) but only shows the new computer in the domain. It "feels" like some security parameter knows the main office is where it safely joined the domain but it refuses all incoming packets when it is at the branch office.

Collapse -

by CG IT In reply to Moving XP client to diffe ...

well something isn't right with your TCP/IP settings. Since your using a static addressing, the symptoms your stating points to the computer being on the wrong subnet. e.g. you send out but do not receive in, therefore packets destined for the computer in question are dropped because it can't be found.

You also state the firewall is disabled, and if you bring it back to main office and just change the settings, network connectivity works fine. Therefore, the problem is at the branch office. Since all you change is the TCP/IP settings, it's got to be those that cause the problem.

Collapse -

by CG IT In reply to

you don't mention DNS server addresses. I would suggest to verify your DNS server addresses.

Collapse -

by LabRaT In reply to

Since workstations running NT Workstation and Win2000 have worked fine with this process, it seems to me it is in the XP SAM/SID setup. Thanks for the suggestions.

Collapse -

by NormH3 In reply to Moving XP client to diffe ...

Sounds as if a road trip to the branch office may be in order. Hopefully it's located in honolulu or miami

Collapse -

by LabRaT In reply to

Thanks. LOL!! Been there twice this week driving 300 miles round trip!! I'm just going to take the system to the branch and rebuild it there so the SAM/SID crap gets set right. This is going to be a pain so I got to find a solution to this configuration problem. I'm leaving the question open in case anyone else has any ideas about moving XP Pro workstations to different locations. My research shows that I should mention the domain controllers are running Windows NT 4.0 platform.

Related Discussions

Related Forums