Opening Ports

Typically, TCP ports 135, 139 and 445 along with UDP port 137

TCP/445 should be enough for mapping. Naturally, you'll need DNS (TCP/53 + UDP/53) to resolve a server name to map to in a domain environment. If the computer is at home (and you don't have a domain), do as @flubbster suggested.

Open all those ports already and still can map via \\computer name\share

Um, let's refine your question... You do not want to be able to map drives to your XP? If so, just close port TCP/445.

I want to be able to map drive to my windows XP.

The drive mapping itself (SMB/CIFS) uses the TCP/445. You can try it by using the IP address to map the drive: \\aaa.bbb.ccc.ddd\share

Can you ping your XP if the firewall is on?

I we are understanding you properly you have a Windows XP machine that you enabled the firewall on. You now are trying to share files from this Windows XP machine to other computer on the network. Is that correct?

If that is the case you shouldn't need to manually create any firewall exceptions. Go into the control panel, Network Connections. Select the connection that you want to share the files on, right click  and select properties. Look for 'File and Print Sharing for Microsoft Networks'. Make sure to put a check mark next to that in order to allow sharing of files from the computer.

This will allow share files from your computer and automatically put the exceptions you need into the firewall for you.

techzter,
Tried out your idea..... still does not work by Computer Name or Ip Address.

Do you receive some sort of error message?

To be clear you did the steps that I had suggested on the machine that you are sharing the from, and not the machine that you are connecting with. Was the file and print sharing not selected before hand? Did the error message change after you had checked it off?

That is correct I followed your instructions to the letter.... Also when I tried to add the ports above Windows said they were already in use.

I am thinking that this may be a bit more involved that just your windows firewall. Have you tried to disable your windows firewall for a moment? If you do that are you able to connect?

Can you give some more information as to how the machines are connected? For instance are they connected to ports within the same swtich?

Are you able to ping between the machines?

If the firewall is down everything works as advertised.  Pinging and mapping drives to the machine work fine.

Once the firewall comes up you can ping... but not map any drives.

They are on different lan subnets.

Well that at least gives us hope that this is only a firewall configuration issue. Let's try this. Go into your windows firewall settings. Go into the advanced tab, and restore defaults. This will help eliminate the chance of a manual entry being made that is causing the firewall access to fail.

After restoring the defaults double check and make sure that it has not removed the access rights for file and print sharing. If so put the check mark back in to enable that access again.

Ok restored the default settings and recheck file and print sharing like you suggested.  Still cant map a drive but I can ping the machine by name though.

Making some progress. So you can ping the machine by name. How about if you go to the run menu and type \\computername or \\ip.address. That should show all of the shares available on the computer. Do either of those connect? If not do you get an error message? If so what is the error?

In both cases the same error comes up "Un able to connect to host"

Strange issue.... not sure whats up... maybe will have the networking guys put a sniffer on it.

That did it.... Thank you very much

Woohoo! Glad to hear that it helped.