"The network path was not found"...

OK, I'm by no means an expert in this field so I feel like a fish out of water, but here goes...
I have been setting up a small network at home, purely for the purposes of learning.
I have 3 PCs:
1) W2K server, successfully configured as a domain controller.
2) XP Pro Desktop
3) XP Pro Laptop

I have managed to get the two XP Pro machines to join the domain. The laptop works perfectly in itself. However whilst the Desktop machine did join successfuly, it cannot access any shared folders/computers/printers etc... It CAN see the server and any users if I search AD for them, but trying to access anything gives a "the network path was not found" error.
The domain controller passes every test in dcdiag and netdiag. I am using DHCP.
The weird thing is, I can successfully ping the server by name from both clients, but when trying to ping either of the workstations by name (whether from the server or a workstation), although the IP address resolves correctly, I always get 4x "The request timed out".
I could go on for ages, but hopefully that describes my problem well enough to get started.
It may be worth mentioning that the Laptop has been configured with mapped drives to the server, and a shared printer, both of which work perfectly.
I'm stumped! It's taken me 3 months to get this far, and I can see light at the end of the tunnel! (I'm not an IT professional)
Any help would be greatly appreciated.
Thanks in advance

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

G'day DaveKB
> I always get 4x "The request timed out".

Ping server from PC workstation = success
Ping workstation from Server = fail

99% of the time this asymetric ping is due to some type of firewall software on the workstation. XP has built-in personal firewall, Norton Internet Security, PC-Cillin even has a built in firewall, as do some VPN clients (Raptor Eagle Mobile and Cisco clients for sure)


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DaveKBAuthor Commented:
Thanks lrmoore. The firewall on the connection is turned off, however, I am running ZoneAlarm on the desktop, and Norton on the Laptop. I am at work now, but will check this when I get home. Could this be the root of the problem?
DaveKBAuthor Commented:
Hey lrmoore, I shut down Zonealarm on the Workstation, and immediately the ping command worked. Started Zonelarm again, got "request timed out" again, so that's definately the cause. Thanks.
Also, with ZoneAlarm shut down, I can now see all network shares and printers.
I would never have thought it couls be that simple!
Thanks my friend.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.