Thanks for the welcome people! I'm have been running 3 servers for several months as a hobby so even though I'm better than my friends, I'm still somewhat novice when it comes to my TCP/IP configuration(s). DNS, Active directory,mx and so on always seem to baffle me! I'm running 3- 2.4 gig servers with server 2k3. I recently downloaded the N-Lite version of 2k3 which I like but it offers almost no driver support. Thats how I found MG, Thank God! I found every driver I needed including my NIC driver and my wireless NIC. I have web access at 108 Mbts but I cannot access my lan no matter what I try. I have RDP access but no file sharing. I can ping the other 2 servers and they can ping me but the problem seems to be in the name translation. The name of this server is "ace-server" but it does not show up on my router interface page nor does it show up anywhere in windows explorer. Here is what I have tried: 1) repair option on my NIC properties - result= "cannot clear netbt" 2) add wireless NIC to compare results - result= same 3) ipconfig - result= Microsoft Windows [Version 5.2.3790] © Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.1.10 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.1.15 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 C:\Documents and Settings\Administrator>nslookup Default Server: dns-cac-lb-02.tampabay.rr.com Address: 65.32.5.75 C:\Documents and Settings\Administrator>nbtstat -a Failed to access NetBT driver -- NetBT may not be loaded:mad: 4) Event viewer - result= Event Type: Error Event Source: NetBT Event Category: None Event ID: 4311 Date: 9/12/2006 Time: 12:59:01 AM User: N/A Computer: ACE-SERVER Description: Initialization failed because the driver device could not be created. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 01 00 58 00 ......X. 0008: 00 00 00 00 d7 10 00 c0 ....×..À 0010: 11 01 00 00 3b 00 00 c0 ....;..À 0018: 03 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ Explanation This is a transient condition that can be safely ignored. NetBIOS over TCP/IP (NetBT) temporarily could not start but it continues trying to start until it succeeds. User Action No user action is required. SYMPTOMS When you upgrade from Microsoft Windows 2000 with Service Pack 4 to Microsoft Windows Server 2003 with Service Pack 1, the following error is logged in the System event log: Event Source: NetBT Event Category: None Event ID: 4311 Date: date Time: time Type: Error User: N/A Computer: computer_name Description: Initialization failed because the driver device could not be created. In this scenario, the NetBIOS transport driver works correctly. You do not experience any network connectivity problems. Back to the top CAUSE Windows logs this event because a non-zero value is incorrectly returned when Windows detects and references the newly introduced network adaptor. The adaptor is redetected as part of the upgrade process. Back to the top RESOLUTION In this scenario, you can safely ignore the Error event. The Error event is harmless. Back to the top STATUS Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Obviously it is infact a problem for me which I have been unable to solve for over 3 days. Can someone help? Thanks, Andy Append: I have come to believe that netbios has deliberately been removed from the registry by WINS haters or whatever but, I need it. I really want to adapt to this N-Lite version but I have to be able to share files with my file, terminal and mail servers.