Have new HP desktop client [10.0.0.x] that will not map shares on server in different domain [192.168.1.x], same company. Can ping server and other servers via IP and name in both domains - OK (thought it may be DNS); but when I open Explorer, the other domain resources are nowhere to be found. Can see and access all resources in the 10. domain fine. Have several other systems accessing from the 10. to the 192. OK -- issue isolated to 1 system. I checked computer (and user) accounts in AD / both domains - OK. Copied Host file from other working 10. x64 system to system after renaming previous Host file. Still no go. Checked settings on the File and Print Sharing - ok there. Checked the MS Forums and most issues seem to be DNS and Active Directory related. Beginning to think it may be possible corrupted Client for MS Networks or File and Print Sharing. Debating on re-image to expedite. Thoughts? Thank you for your time. PS: Checked Firewall and AV - still no go. **************************************** Brought the system back into the 192.168.1.x domain (different building) for re-image and now everything works. Can connect to all resources still in the 10. domain and in the 192. domain. When I was in the 10. domain; I could see the 10. domain - but had issue with the 192.... . Sounds like a routing issue with system, rather than corrupted file(s). System needs to reside in the 10. domain.

Hi, According to your description, I agree with you and also suspect this is a routing issue, it is not related to Windows 7. So check your route list in the router You may also try IP address to access the shared folder of remote computer to see if any error message prompt.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Juke: Your response helped by I did not have to go that far. Was on the Win 7 client, ran route print - checked the active routes... seemed OK. I went and added 2 Persistent routes [ie. route ADD -p 10.x.x.x Mask 255.255.255.0 10.x.x.x Metric #] - that did the trick. Since I had users already connecting, I assumed that the router was OK - unless a MAC address missed a list there. Kept on the client side and can access the needed resources in both domains. Thank you for responding and your time on this. K2JCannon