IT Employment

Ask something
Discussion Locked

Difficulty connecting W2K and XP boxes

0 helpful
1 reply

by mgoldberg

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a 2 machine lan (that will grow to about 10 pcs and several HMI machine nodes) one XP Professional and one 2000 Professional. Both are set up using tcp/ip with the same class C scheme (first nine the same, different last three digits, same subnet mask). The XP machine can get to everything on the 2000 box but not the other way around and I'm quite certain all permissions on the XP box are correct.

When on the 2000 box trying to explore the XP box I get an error saying "Robertson isnot accessible. The list of servers for this workgroup is not available." Robertson is the XP box name and I can see it, just not explore it. I want the server to be on the XP box (since it is stationary and the 2000 box is a laptop). Do I load the ?sever for MS networks? service as on an NT box? If so how?

1 reply

by mrjay67

You might check XPs firewall. I have had odd experiances with it. In your network properties there should be an advanced tab that allows you to check off or on the XP firewall. Turn it off and test things out. You might rebbot the machines to besure after this. If this solves it than you need to configure the Firewall or keep it off.

Otherwise you need to double check all your network settings and possibly reload the network stack. If you are certian that all settings are correct than you might check the NICs. Try switching them and see if the problem follows the NIC. Although You said one was a loptop so this may not be viable. Might try replacing if you have a spare.

If you are just setup as a workgroup make sure the same user login info exists on both machines and the share(s) you are trying to get to.
The problem mostly sounds like a firewall or security configuration issue. You may have to play around with these settings till you get them right. Try making sure its all open firewall permission wise. If this works try locking it back down till you find the problem. If not you know the problem lies elsewhere. Possibly in Network configuration or Hardware issues.

Hope this gets you in the right direction.

Jason

This discussion is closed to new replies.