CMSGT44
asked on
File Sharing On Home Computers
I have gone through the entire process of trying to link up my two home computers to share files/hardware and apparently I'm missing something. Here's what I've done. Computer #1 is running XP Pro (SP2) and Computer #2 is running XP Home (SP2). I ran the Network Setup Wizard on #1 and and turned on the 'file and printer sharing' when asked. I assigned 'HOME' as the workgroup name. I went to #2 and ran the same wizard and followed the same procedures. I restarted both computers as a precaution. When I went to the control panel on #1 and selected my network places, then viewed workgroup computers, #2 is listed. When I select #2, I get an error message which states "#2 not accessible. You might not have permission to use this network resource. Contact administrator of this server to find out if you have access permission. The network path was not found."
When I moved to #2 to view the workgroup computers, #1 was not listed. What am I missing?
Forgot to add. Computer #1 has cable internet access and #2 connects via a wireless Blitzz.
John
When I moved to #2 to view the workgroup computers, #1 was not listed. What am I missing?
Forgot to add. Computer #1 has cable internet access and #2 connects via a wireless Blitzz.
John
The problem could be with the Firewall that is built into windows XP.
you could try disabling it on both PCs for testing purposes.
Start/setings/control panel/windows firewall.
you could try disabling it on both PCs for testing purposes.
Start/setings/control panel/windows firewall.
Home and Pro, eh? Try my P2P troubleshooting page and go through the steps outlined there..
http://65.24.134.81/KipSolutions/P2PNetworks/TroubleshootingP2P.htm
FE
http://65.24.134.81/KipSolutions/P2PNetworks/TroubleshootingP2P.htm
FE
ASKER
Tried all of the above suggestions. NONE worked! Still could not get computer #2 to see #1 in the 'computers in workgroup'. What now????
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
BTW: if you can, take the wifi out of the mix. this is just an extra layer of troubleshooting you don't need right now..
ASKER
For Fatal Exception
Going to go thru all steps again (may have missed something). Going to start with Computer #1. Will let you know.
Going to go thru all steps again (may have missed something). Going to start with Computer #1. Will let you know.
Try accessing the machine using the IP Address from the Run Line... Also, make sure you can ping the remote computer. If you cannot, then it is a routing or Firewall problem.
To use the Run Line:
Start > Run > \\ipaddress (OK)
To Ping, you need to open the command shell:
Start > Run > cmd (OK)
ping "ipaddress"
To use the Run Line:
Start > Run > \\ipaddress (OK)
To Ping, you need to open the command shell:
Start > Run > cmd (OK)
ping "ipaddress"
ASKER
For Fatal_Exception
Thanks a lot! Unfortunately, it was the last item on the list that worked (same as your last comment). How come Microsoft's Network Wizard doesn't work as advertised? Your process is easier and works. Thanks.
John: thechief@charter.net
Thanks a lot! Unfortunately, it was the last item on the list that worked (same as your last comment). How come Microsoft's Network Wizard doesn't work as advertised? Your process is easier and works. Thanks.
John: thechief@charter.net
Hi John! There are many things that come into play when sharing data across a wire, and more when considering wireless. I am not sure whether you are familiar with the OSI model, but when developing an application that takes into consideration everything that must happen at each layer (there are 7 in the traditional model, and each must do it's part) you could see the problems anyone (including the wizards at Microsoft) would have with a one application / do it all / application. Troubleshooting these can also become a nightmare for even the most tested technician, as each layer has it's point of failure.
I am very glad you got it though, and you are welcome to peruse my site anytime you might have some questions. And if it does not help, we are always around in EE to guide you!
Thanks, and have a great weekend!
FE
I am very glad you got it though, and you are welcome to peruse my site anytime you might have some questions. And if it does not help, we are always around in EE to guide you!
Thanks, and have a great weekend!
FE
ASKER
For Fatal_Exception:
I've noticed that now when I go into Internet Explorer or to any other Website, that it's taking an incredibly long time for the page to come up. Not sure which step has caused this. Please advise.
John
I've noticed that now when I go into Internet Explorer or to any other Website, that it's taking an incredibly long time for the page to come up. Not sure which step has caused this. Please advise.
John
None of the steps in that article should result in a change in your surfing, unless your routing tables have been redefined. Try resetting your TCP/IP stack using WinsockFix (on my site). This sometimes fixes these delays.
BTW: is this happening on the wifi connected devices, or all devices?
FE
BTW: is this happening on the wifi connected devices, or all devices?
FE
ASKER
Was on all devices. Already had WinsockFix and ran it. Seems to have fix the problem.
great.. anything else? *grin*
FE
FE
ASKER
Nothiing right now. Thanks loads
John
John
To do so:
Start>Control panel>Network connections
Right-click on the connection u are using. Click properties.
In the general tab, click Internet Protocol (TCP/IP) and then properties.
In the general tab of this window, click advanced...
In the WINS tab, click enable NetBIOS over TCP/IP and then OK.