Something weird with Windows7 Pro. Setting: I have a licenced Windows 2003 Business server on my "digitalsmiles" domain in the basement, and a mix of XP, Windows 7 Pro, imac, iphones, on the home P2P network. For some reason on the Win7 Pro machine I now see two servers when clicking on domain network, both named Server1. However, one shows the name in lower case ("server1"), and the other in upper case ("SERVER1"). Didn't a week or so ago and can't remember what was updated...Microsoft patches? Additional info: On my Win7 Pro laptop it only see's one - upper case version, but this desktop shows the two, meaning it must be a localized issue. As well, my XP Pro's and Apple imac's and iphone's see the server as "Server1". Capital S and lower case the rest. So I click on lowercase and see nothing shared just a blank page, click on the the upper case one and see the shared folders. Then I use UNC to connect to \\server1 and it connects, but nothing showing (as mentioned before), and again use \\SERVER1 and see shared folders. so SERVER1 to Win7 is the correct server name. Can ping both versions and shows same IP address. ...108 Did ipconfig /flusdns, rebooted etc. In the Win7 Network view, even tried details view with mac and ip and both names still show. However when I do a full map view from the Network Sharing Centre, I only see "SERVER1". So how does one delete the 'server1' name from Windows 7, let alone figure out how it got there?

Hi, You may try to disable the Network discovery and re-enable it for a test. Also, you could boot the computer in Clean Boot, this will eliminate the a mount of unuseful network packages. Then you could use the Network Monitor to capture the packages to see what happen at that time. and this behavior can also determine whether the two sever name's destination is same. In addition, the following link for your reference. http://utools.com/help/ErrorDupName.asp Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. Regards, Juke Chou TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease 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.

Hi, You may try to disable the Network discovery and re-enable it for a test. Also, you could boot the computer in Clean Boot, this will eliminate a mount of unuseful network packages. Then you could use the Network Monitor to capture the packages to see what happen at that time. and this behavior can also determine whether the two sever name's destination is same. In addition, the following link for your reference. http://utools.com/help/ErrorDupName.asp Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. Regards, Juke Chou TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com 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. ”

Hi Juke Thanks that worked, turning off Network Discovery and back on again. Thought I did that, but glad it got rid of it. You'd think /flushdns would do it as well. Now I just see SERVER1 as in Win7 (Vista) all computer names are capitalized.