Peer-to-peer conn. problem

  • Thread starter Thread starter Peter Chatterton
  • Start date Start date
P

Peter Chatterton

I have an XP pro SP2 which I'm trying to connect to a tablet PC,
peer-to-peer, with anEthernet cross-over using a realtek NIC on the XP.

They both have a workgroup named MSHOME.

On the tablet, under Explorer>MS Windows Network, there are entries for both PCs.

On the XP, network setup wizard runs okay
but selecting MSHOME under Explorer>MS Windows Network, gives:
"Mshome is not accessible -- maybe need permission."
"List of servers for this workgroup is not avail."

Hope you can help,
Peter
 
Hi
You have to configure the Sharing Permission on both computers.
Hi
Successful Sharing involves some general consideration in Network settings,
http://www.ezlan.net/sharing.html
As well as specific adjustment of each computer according to what it is
allowed to be shared.
Windows XP File Sharing -
http://support.microsoft.com/default.aspx?scid=kb;en-us;304040
Printer Sharing XP -
http://www.microsoft.com/windowsxp/using/networking/expert/honeycutt_july2.mspx
Windows Native Firewall setting for Sharing XP -
http://support.microsoft.com/kb/875357
Jack (MVP-Networking).
 
I have an XP pro SP2 which I'm trying to connect to a tablet PC,
peer-to-peer, with anEthernet cross-over using a realtek NIC on the XP.

They both have a workgroup named MSHOME.

On the tablet, under Explorer>MS Windows Network, there are entries for both PCs.

On the XP, network setup wizard runs okay
but selecting MSHOME under Explorer>MS Windows Network, gives:
"Mshome is not accessible -- maybe need permission."
"List of servers for this workgroup is not avail."
Click to expand...

Peter,

That's a blocked SMB issue, caused by a misconfigured, overlooked, or unknown
personal firewall.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Thanks guys, I appreciate your responses.

I manually configured the lan connections' TCP/IP to 192.168.0.1 &
192.168.0.2 with 255.255.255.0 and the Repair command works on both.
All firewalls are off, there's no active virus checking.
Each PC has sent and rec'd a few hundred bytes.
The PC that's connected to the inet (HP) sees the other one (FUJ)
in My NW Places but FUJ doesn't see HP.

I tried running NW Setup Wiz on HP but it wants an internet connection.
I don't want to do this with the firewalls down.
Turning on the firewalls to send this didn't help with the lan.
What should I do?

Peter
 
Oops! 192.168.0.1 conflicts with the modem.
I tried getting it to obtain automatically but it can't
"Renew the IP @".

Support says it's still manually configured @ 169.254.188.133,
mask = 255.255.0.0, but this doesn't look right.

Peter
 
Sorry, I was a bit confused there, but now I'm back to the beginning with a lan
connection with a TCP/IP of 192.168.0.1 and with a working Repair command.

My question is, why does pinging it time out?

Peter
 
Sorry, I was a bit confused there, but now I'm back to the beginning with a lan
connection with a TCP/IP of 192.168.0.1 and with a working Repair command.

My question is, why does pinging it time out?

Peter
Click to expand...

Peter,

Start from the beginning, and review the process of setting up 2 computers using
a cross-over cable.
<http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html>
http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Back
Top