Sharing files does not work between 2 XP machines?!?

[markjs]

I had the thing up and working and sharing files. The workgroup name is the same, yet all of a sudden it refuses to share files at all. It says maybe I don't have permission to access the shared drives. When I make new drives shared they do not show up. The two machines are linked through a 10/100 router. Anyone have any clues?

 

[spyordie007]

yes, the username you are logged into computer "A" needs to both exist identically (username and password) on computer "B" and needs access to the files.

 

[markjs]

Nope, that's not it. That was already done.

 

[jjyiz28]

what permission did you set on the folder share?

 

[n0cmonkey]

We'll start off at the beginning:
Do the machines connect to the internet fine?
Can the machines ping each other?
Have you made any "administrative changes" on either machine recently?
If you look in the network neighborhood/my network places/whatever it is called today, can the machines "see" each other?
XP Home or XP Pro?

 

[markjs]

The permission I set? All I know is I told it to share the entire drive and allow other users to change the files. Both machines are on the internet just fine. I have made no administrative changes. I do not think the machines can see each other in "My Network Places" but on one machine it remembered that there used to be a shared drive and it still lists it although it cannot connect to it. I don't know how to ping between the machines. And it is XP Pro.

 

[markjs]

OK I just hit run>cmd and ping 192.168.0.101, and it sent and recieved 4 packets so I am assuming that means the computers are connected. Strangely though you cannot ping this machine from the other one, but only ping the other one from this one.

 

[jjyiz28]

Originally posted by: markjs
OK I just hit run>cmd and ping 192.168.0.101, and it sent and recieved 4 packets so I am assuming that means the computers are connected. Strangely though you cannot ping this machine from the other one, but only ping the other one from this one.

make sure that both pc are on the same network. im assuming the 192.168.0 network. also, if you're running software firewall, disable it for now just to see if its impeding it

 

[markjs]

So I have taken all the advice and still the problem exists. I can ping 192.168.0.101 from 192.168.0.102, but not vice versa, and I cannot ping either machine by the computer name.

I guess the next step is what it always is.....Complete Windows reinstall. I don't see anyone having an answer to my seemingly nonexistant problem.

 

[spyordie007]

Part of the problem is that you are giving nearly useless information. Take your time answering our questions and we will be better able to help you. I do not believe reinstalling Windows is neccisary, this is generally the desperate attempt of someone who doesnt understand what they are dealing with. Think carefully, explain completly, listen closely and we can probably help you solve this problem without a reinstall of windows.

If you are able to ping one machine from the other but not vice versa please list the following information for us for each machine:

how are the IP addresses set, statically or are they assigned from a dhcp server?
do an ipconfig /all and give us:
Ip address
subnet mask
gateway
dns server(s)
computer name
workgroup name

after getting that information we will proceed.

 

[markjs]

OK but I am telling you that there is no problem with all that stuff I am not stupid......I assumed you'd know I got these things right before I came to you.. To prove it here are the numbers

Workgroup for both computers is REMARKABLE

Computer 1.
Name: mjs-1
IP: 192.168.0.102
Subnet Mask: 255.255.255.0
Gateway, DHCP and DNS: 192.168.0.1

Computer 2.
Name jvb
IP: 192.168.0.101
Subnet Mask 255.255.255.0
Gateway, DHCP and DNS: 192.168.0.1

Both machines are set to allow DHCP to assign IP.

So you tell me, why in the hell don't they work? The settings are all correct, the connections are all fine or one or both machines would lose internet connectivity. I know enough about networking to know that there is theoretically no problem with my network other than the fact it doen't work!

 

[spyordie007]

I'm not saying you're stupid, just that you're human. If i had a dime for every time I thought I had everything right only to find out I didnt upon closer inspection I would be very rich by now.

Let's start by ensuring basic TCP/IP functionality because it sounds like that could be the root of your problem. Do an ipconfig /release on both computers (just release and DO NOT RENEW YET). Than power down that router for a good 10 seconds and boot it back up. Once the router is rebooted do an ipconfig/renew on both machines and ensure they have both recieved IP addresses.

Assuming they have both recieved IP addresses from the router trying pinging one from the other, if they are not able to ping eachother try having them ping themselves (by the IP they recieved) and report back the results.

 

[markjs]

After rebooting and renewing, results still the same my computer can sill ping the other but the other cannot ping mine. When pinging themselves everything works fine. Both machines of course ping the router just fine. So basically everything is right cept it don't work! See what I mean about a non existant problem?

Edited to say: I tried rebooting the router and changing the plugs the two comps were plugged in at....Same result!

 

[spyordie007]

it sounds like one of them is not responding to network traffic properly, is it possible you have a firewall installed on one of them?

If not it's possible that TCP/IP is malfunctioning on one of them. If you have a 3rd machine at your disposal it would be easier to determine which one, however my guess would be that it is the one that you can ping from but not to (as in it's not responding correctly) but it's possible that it could be the other way around. If it is indeed a TCP/IP issue it could probably be fixed by running netsh:
http://support.microsoft.com/?kbid=299357

Just keep in mind that running netsh is going to blow away all your TCP/IP settings (which probably wont be an issue for you, but thought I should mention it).

 

[markjs]

I tied that netsh, and absolutely zero result except a nice little log file being created. Didn't even disrupt the internet. I am at wits end, and I am seriously getting close to complete windows reinstall on both machines.

 

[spyordie007]

will you post the netsh logs from both machines?

 

[josphII]

enable the guest account in computer management

 

[markjs]

The first machine:

reset SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\15\RegLocation
old REG_MULTI_SZ =
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpDomain
SYSTEM\CurrentControlSet\Services\TcpIp\Parameters\DhcpDomain

added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{68894FCE-F78D-4D50-91CB-E86947898142}\NetbiosOptions
added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{D73E62F7-226F-4494-8988-44A5E7238110}\NetbiosOptions
deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts
added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{753D787B-2776-486D-AB20-26E319E44320}\DisableDynamicUpdate
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{753D787B-2776-486D-AB20-26E319E44320}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{753D787B-2776-486D-AB20-26E319E44320}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{753D787B-2776-486D-AB20-26E319E44320}\IpAutoconfigurationSeed
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{753D787B-2776-486D-AB20-26E319E44320}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{753D787B-2776-486D-AB20-26E319E44320}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{753D787B-2776-486D-AB20-26E319E44320}\UdpAllowedPorts
old REG_MULTI_SZ =
0

added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{7A93A39F-B529-43F6-80C6-F14293157C8E}\AddressType
added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{7A93A39F-B529-43F6-80C6-F14293157C8E}\DisableDynamicUpdate
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{7A93A39F-B529-43F6-80C6-F14293157C8E}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{7A93A39F-B529-43F6-80C6-F14293157C8E}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{7A93A39F-B529-43F6-80C6-F14293157C8E}\UdpAllowedPorts
old REG_MULTI_SZ =
0

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution
reset Linkage\UpperBind for PCI\VEN_10DE&DEV_0066&SUBSYS_10001695&REV_A1\2&EBB567F&0&20. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =
PSched

<completed>



The second machine:


reset SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\15\RegLocation
old REG_MULTI_SZ =
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpDomain
SYSTEM\CurrentControlSet\Services\TcpIp\Parameters\DhcpDomain

added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{00FC82C9-CD8C-40EB-92F6-5C0A5ADFCCD2}\NetbiosOptions
added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{9B09855F-AA43-4818-9979-76048A388BF5}\NetbiosOptions
deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts
added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{85CD316B-EB6E-4D16-A961-B191E5BB7036}\AddressType
added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{85CD316B-EB6E-4D16-A961-B191E5BB7036}\DisableDynamicUpdate
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{85CD316B-EB6E-4D16-A961-B191E5BB7036}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{85CD316B-EB6E-4D16-A961-B191E5BB7036}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{85CD316B-EB6E-4D16-A961-B191E5BB7036}\UdpAllowedPorts
old REG_MULTI_SZ =
0

added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E854D085-94D2-4551-8162-A5BD5946BC0C}\DisableDynamicUpdate
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E854D085-94D2-4551-8162-A5BD5946BC0C}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E854D085-94D2-4551-8162-A5BD5946BC0C}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E854D085-94D2-4551-8162-A5BD5946BC0C}\IpAutoconfigurationSeed
reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E854D085-94D2-4551-8162-A5BD5946BC0C}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E854D085-94D2-4551-8162-A5BD5946BC0C}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E854D085-94D2-4551-8162-A5BD5946BC0C}\UdpAllowedPorts
old REG_MULTI_SZ =
0

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution
reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\2&EBB567F&0&88. bad value was:
REG_MULTI_SZ =
PSched

<completed>

Does this help?

 

[spyordie007]

Originally posted by: josphII
enable the guest account in computer management

How is that going to help his ability to ping?

Mark, I should have a few min. tomorrow afternoon and I'll review the logs and see what I can come up with. I'm surprised you're still having troubles.

-Erik

 

[TEEZLE]

This is probably a stupid answer, but I had the same problem as you. I added the IPX/SPX protocol under the connections on each machine and now I can see both machines. Have you tried that yet?

 

[spyordie007]

That?s not a stupid answer, installing another protocol such as IPX/SPX would circumvent his problem.

 

[markjs]

Once again no dice. Adding IPX/SPX did nothing. I may do the complete reinstall as early as this afternoon.

 

[spyordie007]

what? it's another protocol altogether!

New troubleshooting step for you to take, get a stand-alone hub or switch and hook the 2 computers directly into it. Hardcode their TCP/IP settings and see if they can ping eachother.

 

[markjs]

Once I told it to search for the other computer it found it. Adding IPX/SPX did finally solve the problem after all. Thank you all so much, especially spyordie007.

 

[spyordie007]

glad you're finally up and running!