Posted 03 November 2010 - 07:51 PM
Here is my story:
Once upon a time I had two computers both running windows XP service pack 3 on one network, my laptop uses a wireless connection and my tower uses a wired connection. At one time I had happy little mapped drive on my tower to connect to the C: drive of my laptop so I could mooch files. When it didn't work one day I disconnected the mapped drive in an effort to fix it. So, logically, I went back to try to Map the drive and clicked on the appropriate area in the menubar of My Computer. A convenient window pops up for me to select the drive letter that I would like to assign and a folder that I would like to map. I click browse because it is easier to not move my other forearm. So I click "+Entire Network" "+Microsoft Windows Network" then "+MSHOME" which is my workgroup name. The only thing that shows up is my tower, which is the computer I happen to be working from. My Laptop's name is not in the list. "Interesting," I say.
I then go to the laptop and am curious to know if it is just being prudish with my tower and asserting its superiority. I try to map a drive from my tower onto my laptop. Using the same browse technique as to not strain any muscles, I find my tower sitting there ready to be entered willing to map any drive my laptop desires. "Hm." So I decide to use some of my limited knowledge of the command prompt and see if I can muster of some kind of response from my laptop via the tower.
After some pings from my tower to my laptop I find that the first one or two pings usually Time Out, but the rest connect and respond. A ping from my laptop to my tower responds promptly with all responses.
Net View responds with
"\\Tower" from the tower and the laptop.
So after an hour of Googling I found no answer that worked. Both computers are in the yard disassembled thinking about what they have done. When I put them together I will need some help figuring this out, any ideas?