Windows XP Computer Can't Be Seen Properly on Network

I installed Windows XP Pro fresh on a new machine I built at home. I'd done this several times in the past and was able to successfully see all those machines on the network with no problem.

This one was different, however. I could do everything I wanted from this particular machine to the others in my network (pushing/pulling files to other shares on other machines), but I couldn't get the others to talk to this one.

The only difference with this computer's install was that it was done from the Windows XP SP3 CD. My prior installs were done on earlier XP versions.

It seems the SP3 CD will firewall your connection by default and NOT count "File and Printer Sharing" as an exception.

To resolve it, you need to get that Exception enabled (recommended) or disable your Windows Firewall for the connection (not recommended).

To enable the exception in Windows Firewall (assuming Windows Firewall is enabled on the connection):

1. Open Network Connections (Start >> Settings >> Control Panel >> Network Connections; or use your favorite quicker means...)
2. Right-click the offending connection >> Properties >> "Advanced" tab
   
3. Click the "Settings" button for Windows Firewall >> "Exceptions" tab
   
4. Check the "File and Printer Sharing" checkbox
5. Click OK on the Windows Firewall dialog.
6. Click OK on the Connection Properties dialog.
   

Screenshot
in the non-working state
(click to see full-size)

You should now be able to ping the computer by name and access its file shares, etc. on your network.

ATi Catalyst Display Driver Issue: "CRT invalid display type" on Windows XP

Catalyst Display Driver 7.7 and higher

When a digital panel is connected to a Radeon graphics card between Radeon models 9500 and HD2900 (including X300 through X1950) you will see many errors in the Windows event log listed as "CRT invalid display type"; with the source being "ati2mtag".

AMD/ATi has known about this issue since the end of August 2007 and has supposedly been investigating it. I don't know that they have discovered a fix yet as I just downloaded the newest drivers from last December and have these errors popping up in my own event viewer (hence my own Google chase.)

I figured I would try to save others some trouble. Click the link above to get updated information if/when it arrives. At the time of this posting, the article has been viewed 18227 times and only modified once, the day after the original post. I guess they haven't figured it out yet. :)

Their solution is to install Catalyst version 7.6; and they say it won't cause issues to the system or performance (though from my Googling, it sounds like many have had system hangs/random reboots/screen blankouts because of it.) Your mileage may vary. I haven't seen any reboots myself.

Please comment on your experiences with this issue and any better solutions (if any) you've found.