I have several Windows 7 machines in my store, none of which seem to authenticate with my server. It is the same username and password I always use. The server is Windows 2000 Standard. However, I can reload the Windows 7 on the machines, and then it seems to work fine. Is there anything I can do to fix the issue without reloading Windows over and over?

Can you please provide more information about your setup, specifically the network arrangement, what routers and other hardware are in use, how IP addresses are allocated, whether you're using domain authentication, etc. Thanks -- James McIllece

Besides the above quesstions, please let us know what error message is received. Please also check if the following thread will help.http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/f946773b-5e24-4c63-8655-4ac2bd79c5e8 Vivian Xing - MSFT

Can you please provide more information about your setup, specifically the network arrangement, what routers and other hardware are in use, how IP addresses are allocated, whether you're using domain authentication, etc.Thanks --James McIlleceThe setup is a basic network, layed out as follows. Firstly, there is our modem (Comtrend Ct-5071T) which is hooked to our router(D-Link WBR-2310). The router is hooked to a switch to give us enough ports for all of our systems, and customer computers. It is a 24 port switch (D-Link 1026G) There are 2 Gigabit ports on this switch, one of which is hooked to another 8 port gigabit switch (DGS-1008D) for our 4 Office computers only.The 24 port switch is routed through the floor to provide ethernet to our workbench in the back room, and to 3 places up front for quick fixes.IP Addresses are set in IPv4, and are allocated by the router with DHCP. The server has a static IP set of 192.168.0.150, and the printer server is set to 192.168.0.151I should note that I have no issues getting to the server with any Vista machines or XP machines. Some Windows 7 machines have been known to work as well, but only after reloading the operating system.

Besides the above quesstions, please let us know what error message is received. Please also check if the following thread will help.http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/f946773b-5e24-4c63-8655-4ac2bd79c5e8 Vivian Xing - MSFTWhat happens is, in the search box at the bottom of the start menu, we type in our server address by name. It brings up an authentication screen where we typically just have to enter a user name and password. The password has not been changed as it works on XP and Vista machines. When we enter it, we have been getting user name/password incorrect.I'll check out that link provided as well, thanks!

When you reload the operating system how do you do this? With a Windows DVD or a manufacturer's restore media? Do you reload the same security software? Is the Windows 2000 server a domain controller? If so are the Windows 7 computers joined to the domain?Kerry Brown MS-MVP - Windows Desktop Experience

When you reload the operating system how do you do this? With a Windows DVD or a manufacturer's restore media? Do you reload the same security software? Is the Windows 2000 server a domain controller? If so are the Windows 7 computers joined to the domain?Kerry Brown MS-MVP - Windows Desktop ExperienceBasically, the first load that doesn't work, and the reload that does work are the same setup. Before I have even loaded any updates or software, I have gotten into the habit of checking the server so that if I do have to reload, I can do it right away and not lose any work or time.I am using an OEM disk, brand new, just opened. I reload with the exact same CD. The server is not a domain controller.

That sounds like a driver problem. Make sure you have the latest driver fo the NIC then try again. If the NIC is a Broadcom or Intel you may have to disable TOE in the NIC driver propertities.http://msmvps.com/blogs/bradley/archive/2006/11/10/Broadcom-Nic-issues.aspx#469535The link is about servers. The problem exists on Windows clients as well. Kerry Brown MS-MVP - Windows Desktop Experience