xp pro peer-to-peer issue
This one's eluding me. Two systems with almost identical specs ie:
asus p4s800 MainB
P4 3GHz 800
512 3200 ram
are connected thru a crossover cable. Both have XP Pro SP1 and no Firewall software installed. There is no internet connection and IP addresses are 198.162.0.2 & 198.162.0.3 with a subnet mask of 255.255.255.0 and both are members of the the workgroup MSHOME. One is named FIRST and the other SECOND. Both have been configured with 5 users all with passwords
If I bootup FIRST and logon then bootup SECOND and logon as a different user then explore MSHOME in FIRST with windows explorer I can see both FIRST and SECOND. But if I click on SECOND I get an access denied error. Then when I explore MSHOME from SECOND I get an access denied error to the workgoup in general. This also works the other way around:
If I bootup SECOND and logon then bootup FIRST and logon as a different user then explore MSHOME in SECOND with windows explorer I can see both FIRST and SECOND. But if I click on FISRT I get an access denied error. Then when I explore MSHOME from FIRST I get an access denied error to the workgoup in general.
When I ping from either computer to the other computer the request times out.
Anyone know what's going on?
asus p4s800 MainB
P4 3GHz 800
512 3200 ram
are connected thru a crossover cable. Both have XP Pro SP1 and no Firewall software installed. There is no internet connection and IP addresses are 198.162.0.2 & 198.162.0.3 with a subnet mask of 255.255.255.0 and both are members of the the workgroup MSHOME. One is named FIRST and the other SECOND. Both have been configured with 5 users all with passwords
If I bootup FIRST and logon then bootup SECOND and logon as a different user then explore MSHOME in FIRST with windows explorer I can see both FIRST and SECOND. But if I click on SECOND I get an access denied error. Then when I explore MSHOME from SECOND I get an access denied error to the workgoup in general. This also works the other way around:
If I bootup SECOND and logon then bootup FIRST and logon as a different user then explore MSHOME in SECOND with windows explorer I can see both FIRST and SECOND. But if I click on FISRT I get an access denied error. Then when I explore MSHOME from FIRST I get an access denied error to the workgoup in general.
When I ping from either computer to the other computer the request times out.
Anyone know what's going on?
-Ensure the cable is crossover and functioning
-Ensure both nics have the link light on
-Disable the integrated sweet sweet windows xp firewall
-Try running the Windows XP network configuration wizard in the My Network Places window. As it default disables all file sharing and communication to the PC.
As good as the Microsoft articles are. Far too much reading.
-Ensure both nics have the link light on
-Disable the integrated sweet sweet windows xp firewall
-Try running the Windows XP network configuration wizard in the My Network Places window. As it default disables all file sharing and communication to the PC.
As good as the Microsoft articles are. Far too much reading.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Dear All,
I have read all through all the articles and related articles (thank you mattisflones) it was great help. My earlier search on the microsoft support site didn't yield as great a success. This is what the prob was:
One of the systems had an ASUS P4P800 Motherboard. Excellent performance, great chipset and integrated with a 3Com network controller. Unfortunately on start up it stated a new CPU had been detected every time and reverted to defaults then kept spontaneously restarting or freezing, anywhere between a minute and a couple of days after start up, a prob I couldn't emulate. I replaced it with an ASUS P4S800, not as good, no SATA and it was integrated with a SIS network controller. Upon start up it detected the network controller and installed it but the DNS server and DHCP controller remained configured to the 3Com NIC which no longer existed on the system. I had been meaning to do fresh OS install on this box anyway and did so. Prob solved. I just wanted to know what it was before doing so, I like coming accross unknowns.
I have read all through all the articles and related articles (thank you mattisflones) it was great help. My earlier search on the microsoft support site didn't yield as great a success. This is what the prob was:
One of the systems had an ASUS P4P800 Motherboard. Excellent performance, great chipset and integrated with a 3Com network controller. Unfortunately on start up it stated a new CPU had been detected every time and reverted to defaults then kept spontaneously restarting or freezing, anywhere between a minute and a couple of days after start up, a prob I couldn't emulate. I replaced it with an ASUS P4S800, not as good, no SATA and it was integrated with a SIS network controller. Upon start up it detected the network controller and installed it but the DNS server and DHCP controller remained configured to the 3Com NIC which no longer existed on the system. I had been meaning to do fresh OS install on this box anyway and did so. Prob solved. I just wanted to know what it was before doing so, I like coming accross unknowns.
:-) Glad i could be of some help, and thanx for the good update on your problem.
Too few askers posts such good explainations back! and we really apreciate it... Its very valuable for us and anyone that might browse through the article later.
Too few askers posts such good explainations back! and we really apreciate it... Its very valuable for us and anyone that might browse through the article later.
Try these for a start:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314067
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308007