XP Pro cannot see or connect to Windows 7

[baroncaudill]

I have a new Win 7 system hosting an application via file share, with four clients systems (2 Vista) (2 XP). All systems are members of the same work group and the Vista stations can connect to the Win 7 host without issue. However my 2 XP boxes cannot fileshare with Win 7 host.

I have made sure that the permissions are correct that is somewhat established with fact that my 2 Vista boxes can connect to the same share.

Any feedback would be much appreciated.

 

[kegobeer]

Do the XP machines show up in the Windows 7 network neighborhood? Does the Windows 7 machine show up in either of the XP network neighborhoods? Are all computers part of the same workgroup?

 

[aem]

Can you ping the w7 machine from your Xp ones?

 

[baroncaudill]

Both XP boxes can be seen from the Win 7 (they all are part of the same work group) but the Win 7 box cannot be seen from the XP boxes. The Win 7 box can be pinged from the XP boxes but not viewable on the Network.

 

[kegobeer]

Do you have identical users and passwords on all machines? If not, try creating the same user on the XP machines and the Win 7 machine.

 

[baroncaudill]

I already tried to old identical users and passwords trick on all machines.

 

[kegobeer]

Have you disabled homegroup on the Windows 7 machine? Have you tried disabling ipv6 on the Windows 7 machine?

 

[baroncaudill]

The entire network is running only on IPv4 and HomeGroups started off disable; tried enabling and now is back to disabled.

 

[mushroomboy]

Is the Win7 network private or public? I had a bitch of a time getting the computers to work last time I did something like this. Though the sharing protocalls are different I believe and you might have problems. =( It has to do with Win7 using a private network, but as far as file sharing it's a bitch.

 

[rrfranczak3]

my problem is exactly opposite my Mini 10, we will call that machine (netbook) is on Win 7 ult and the desktop across the network is on xp pro we will call that machine (server), the netbook can not see the server, I can ping it and also ping the printer which is on the network with its own static IP, but cant print to it, homegroup on the netbook is disabled, if I boot into xp on the netbook all works perfect..printing and all..on win 7..nothing...this cant be this difficult...there must be a problem with win 7..I have read about a lot of others having similar issues...hope that SP1 coming out addresses this..outside of that I love win 7, I know I could load win 7 on the server and use homegroups, but not ready for that yet..what I am trying to do should just work....any ideas?...anyone????????

 

[kegobeer]

The entire network is running only on IPv4 and HomeGroups started off disable; tried enabling and now is back to disabled.

You haven't said if the XP and Vista machines can talk to each other. Any problems with Vista to XP communication?

 

[mushroomboy]

Share Files and Printers between Windows 7 and XP :: the How-To Geek

 

[baroncaudill]

I just had success getting the XP box to see and connect to the Win 7 box by removing the XP machine from the workgroup and connect via IP.

 

[mushroomboy]

A quick work around I would do is set up FTP servers, that way it's more secure than just windows file sharing. It also works no matter if it's on XP/Vista/Win7... I like to have one machine as a main server to store files (when I have the money... )

 

[baroncaudill]

Thanks for the advise on FTP however that does not apply to this case if you read the full description this is a fileshare so that an application can be ran on multiple clients hosted from a single point of install.

 

[mushroomboy]

I have a new Win 7 system hosting an application via file share, with four clients systems (2 Vista) (2 XP). All systems are members of the same work group and the Vista stations can connect to the Win 7 host without issue. However my 2 XP boxes cannot fileshare with Win 7 host.

I have made sure that the permissions are correct that is somewhat established with fact that my 2 Vista boxes can connect to the same share.

Any feedback would be much appreciated.

He says hosting an application via file share, I didn't know he is installing it on one computer to run on multiples. In context you can host an application and still be meaning just to host it so they can install on their own computer. Though He could run a SAMBA share so that the other computers see it as a drive if I'm not mistaken.

 

[baroncaudill]

The entire network is running only on IPv4 and HomeGroups started off disable; tried enabling and now is back to disabled.

You haven't said if the XP and Vista machines can talk to each other. Any problems with Vista to XP communication?

I haven't focused much on the communication between the clients (XP to Vista) but the Win 7 box can communicate with the XP, so reason would suggest a similar communication between XP and Vista.

 

[kegobeer]

Verify that the XP and Vista machines can communicate (XP can access Vista and Vista can access XP). When dealing with networking, never assume anything.

 

[mushroomboy]

They can, it's just a bitch. I was sharing internet with another computer once... ICS through wireless, and we would have to have him set up the wireless channel and me connect to it for ICS. Yet I'm the one who should be starting the wireless, ugh whatever we bought a router.

 

[Zardoc]

This maybe a shot in the dark but it worked for me with my XP boxes.

Follow these steps to check for problems on the machine you cannot access.
1) Open the registry editor on the machine you cannot connect to by clicking on Start, Run
2) Type REGEDIT and press Enter
3) Click on the plus signs (+) next to the following entries
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
Lanmanserver
Parameters
4) In the right-hand portion of the Registry Editor look for a key called IRPStackSize
5) If the key exists, double-click on it and increase the decimal value to 15 and click OK. Close the Registry
Editor, reboot the computer and try to connect to the network
share. If you are still unable to connect follow the above steps again and increase the decimal number for
IRPStackSize by 5 and try again. Continue to do this until the
stack size is large enough to permit access. Personally, I had to increase the number to 25 before I could connect.
The decimal range for the parameter is between 11 and 50.
6) If the IRPStackSize key DOES NOT exist in the right-hand column of the registry editor, then click on
right-click in the blank area in the right-hand column and choose
New
7) Then Click on D-Word under the Key column
8) In the Name of the new key, type the name IRPStackSize and press Enter. Type the name with the correct
capitalization as shown above.
9) Now double-click on the IRPStackSize key and type 15 in the value data box and place a dot next to Decimal then
click Ok.
10) Close the registry editor and reboot the computer. Try to access the network share again. If the same error
appears follow the steps above to increase the value and
reboot again. Continue this procedure until the problem is resolved. The decimal range for the parameter is between
11 and 50.