16 total posts
As stated in the original post...
...the Windows firewall is turned off on both machines. The router is not a router, but rather a Linksys switch, so no way to set it to DHCP. The ethernet cards are configured with a static IP on the same subnet. Again, I can ping each machine from the other, BUT I CAN'T MAP A DRIVE. This is extremely frustrating, as I have never had this problem before and I can't seem to figure it out. Does anyone have any more ideas. What should be a simple procedure has become a pain in the............
Any and all help appreciated!
And as discussed, there are many prerequisites for sharing.
You listed only the firewall, but rather than going over each item with each member I offer the prior discussion so they can check over accounts and that issue with re-sharing.
Your reply doesn't tell much about the other areas.
OK...I checked the previous post....
...and I have been going around and around and around with this problem for about 2 weeks now, and I am still beating my head against the same (fire)wall... The same user account exists on both computers, both with admin priviledges. The drives I want to map to have been fully shared. Both ethernet cards are configured with static IPs on the same subnet. I can ping each machine from the other. The Windows firewall has been turned off on both machines, but I still can't map a freakin' drive!!! "The network resource cannot be found." Can anyone provied a clue as to what might be going on before I take a hammer to both machines? I have been networking various home computers for years and I have never had this problem before, so I am really frustrated and at a loss as to what is going on. Could it be a hardware problem of some sort? Or some mysterious Windoze tweak?
"The router is not a router, but rather a Linksys switch"
Ouch. Expert setup mode.
OK, without knowing the setup in detail I'll just write it shouldn't work. Not everyone gets it right. Also, any use of ICS trumps the sharing and may disable this.
I'm also sensing this is some homebuilt machine. Again the details are missing so I can't guess if you forgot some motherboard driver.
Not sure what other details you need, Robert...
But once again, both machines are running XP. Both have the same user account with admin privileges. The drives I am trying to map to are fully shared with all read, write and change permissions granted to various users. I am now using a Netgear VPN Router/Firewall running DHCP. Both ethernet cards in the respective machines are configured to acquire an IP address from the DHCP server (Netgear Router). Once again, I can ping each machine successfully from the other. And when I open a RUN dialogue box from the start menu and type in the IP address of the other machine, I get an explorer window showing all the shared files and folders on the other machine, which I can manipulate at will. However, whenever I try to map a drive I still get the error message that the network resource cannot be found and I may not have access permissions to connect to that resource. Hmmmmmm.... Most peculiar. Some problem with NetBIOS name resolution???
Sounds like a tweaked machine. You did..
Reveal a clue. I've seen that happen when the owner hid the network neighborhood from the desktop. But I'm guessing here. Is this "stock" or tweaked?
I still see no response about the long discussion where we covered almost all the angles from accounts to firewalls.
...I read through the previous discussion AGAIN and I see nothing there that I have not already touched on. To reiterate: The same user account is on both machines, with admin privileges. Windows firewall is turned off on both machines, Zone Alarm shut down. Both ethernet cards configured to receive an IP address via DHCP from the Netgear VPN firewall/router. I can successfully ping each machine from the other. I can type the other machine's IP address at the RUN command and view all the shares on the other machine. I just can't map a drive!
And yes, both machines are heavily tweaked. I am running TweakUI and a couple other tweak programs, but My Network Places is still on the desktop, although I may have removed it at one time. Why should this matter?
The two items you didn't write about are:
1. Recreating the share after the accounts were made. Even if you did so, it's time to recreate it.
2. If the IP address works but the name doesn't then I wonder if someone was tweaking XP Services. I can't guess what's different from stock but one service provides name resolution. Maybe someone stopped that?
Sorry, I take these setups on stock XP setups and it works. Once we run into tweaked machines it's too much fun to find what it is.
The accounts have been on the machine...
...since I bought or built them. And I have been all through the Services several times. The only one that I can find which relates to name resolution is TCP/IP NetBIOS Helper, which is turned on on both machines. I will try re-creating the shares...
Thanks for all your help.
That other service?
I believe has the letters DNS in it may be needed. Check to see which are not in the stock settings.
Both of those services are running, and...
...re-creating the shared drive has made matters worse. Now I cannot even connect to the shared drive with the IP address at the RUN command anymore. All I can connect to is some generic shared folders. I am completely frustrated and at a loss as to why these two machines are unable to connect on my home network. Time to get out the sledgehammer...
Now that's interesting.
If recreating the share made it worse, it could have been insightful to know the error messages when you connected with the ip address.
It certainly reads like the age old issues of name resolution and accounts.
I don't get an error message...
...when connecting with the IP address at the run command. The error message appears whenever I try to map a drive in Explorer or when I try to map a drive or find the shares in Workgroup in My Network Places. The error states that the network path could not be found, or perhaps I don't have permission to access that resource, and it urges me to contact my network administrator. Well...that's me! Great advice, Microsoft!