Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Wednesday, November 17, 2010

Networking Windows Server 2003
"User has not been granted the requested logon type at this computer" 
when trying to map a drive
MS error Event ID: 4311
This error can occur because of an incorrect registry setting.
The value for HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\TransportBindName can be blank. Set it to "\Device\", reboot.
Try running nbtstat -n on the server. It should display something like this where the serverName parameter can be seen (in this case the localhost was named ALF33ENT and the serverName parameter was set as above with a trailing A on the end).
Nbtstat alfresco on.jpg
If you are running Windows 2003 and get an error like Failed to access NetBT Driver - NetBT may not be loaded, you may not be logged in as an administrator. You must be an administrator to run nbtstat. If you are still getting this error, you might want to reset your network settings. You can do this by running the command netsh int ip reset c:\reset.log and rebooting. Before doing that - Please note that this will reset your TCP/IP settings and your IP address will be set to DHCP if it was static before. Therefore, make sure you copy down your static IP addresses and nameserver settings and have a way to connect back to the server. After the reboot, you can reset your static IP and name servers.
Folder Share In Workgroup
I did. "Everyone" has read permission in sharing, and only Ted (& admin) have full rights in security. But Ted can only open files "read-only"
It is because Computername/Ted (which he is using) is not the same thing as Servername/Ted which only exists on the server and is the account that has the rights.
My "workgroup" techniques may be a bit rusty but if the Workgroup Names on all machines match and if the accounts on all machines are spelled the same and if the matching accounts also use matching passwords then it should work transparently.
But if that all still doesn't work just make the server a DC, join the workstations to it, and be done with it. As long as you keep the Domain design simple and don't try to do more than you know how to do, is *easier* to work with a Domain than it is to work with a workgroup.
The names & passwords DO match, just the local domains are different for the PC & server.
You mean the Workgroup Names? There is no such thing as a "local domain".
The name need to match,....Ok,..well they don't *need* to match,...but see where I'm going here?,...I am trying to create a simple, straight-forward, non-vague, "by-the-book" situation here so that it is easier to troubleshoot.
This is such a small setup - just 3 PCs - I didn't bother with a DC as it seemed hardly worth the effort & of no use.
A DC is almost *always* worth the effort no matter how small the situation is. 
The real determing fact is the cost of another machine and the Server OS and if the people using it have enough skills to at least use it at a basic level. If you keep it simple it doesn't take much knowledge.
Workgroups are *always* more trouble to deal with. I thought maybe it would ask for an additional login, but it just opens the folder & makes the files read-only.
The only other thing I can think of is errors in the Permissions. Double check them.
*Remember* that Share Permissions do not effect the NTFS Permissions. 
You can grant every Share Permission in the world to the user,...but yet the NTFS permissions can still not allow anything other than Read-only. 
The Share Permissions and the NTFS Security are two different things and you must set them both properly.
There are two places you need to assign rights:
Sharing and security. Make sure you assign permissions in both. 
HOW TO: Configure TCP/IP Networking While NetBIOS Is Turned Off on a Server Running Windows Server 2003
This step-by-step article describes how to configure a computer running Windows Server 2003 with TCP/IP networking while NetBIOS is turned off
HOW TO: Determine Which Program Uses or Blocks Specific Transmission Control Protocol Ports in Windows Server 2003
This step-by-step article discusses how to determine which program uses or blocks specific Transmission Control Protocol (TCP) ports. The Netstat.exe utility has a new switch, the -o switch, that can display the process identifier (ID) that is...
HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows Server 2003
This article tells how to diagnose and test Transmission Control Protocol/Internet Protocol (TCP/IP) or NetBIOS network configurations. It also tells how to use of the most common diagnostic tools and provides basic network analysis techniques
HOW TO: Enable TCP/IP Forwarding in Windows Server 2003
By default, TCP/IP forwarding is turned off (disabled) in Windows Server 2003. This article describes how to enable TCP/IP forwarding on a Windows Server 2003-based computer.
HOW TO: Harden the TCP/IP Stack Against Denial of Service Attacks in Windows Server 2003
Denial of service (DoS) attacks are network attacks that are aimed at making a computer or a particular service on a computer unavailable to network users. Denial of service attacks can be difficult to defend against. To help prevent denial of service attacks, you can harden the TCP/IP protocol stack on your Windows Server 2003 computers. The default TCP/IP stack configuration is tuned to handle standard intranet traffic. If you connect a computer directly to the Internet, Microsoft recommends that you harden the TCP/IP stack against denial of service attacks.
HOW TO: Remove and Reinstall TCP/IP on a Windows Server 2003 Domain Controller
This article describes how to remove and then reinstall TCP/IP on a Windows Server 2003 domain controller. When you troubleshoot an issue, you may suspect that a TCP/IP-related component is either corrupted or damage
How To Install and Configure a DHCP Server in a Workgroup in Windows Server 2003
This step-by-step article describes how to configure a new Windows Server 2003-based Dynamic Host Configuration Protocol (DHCP) server on a stand-alone server to provide centralized management of IP addresses and other TCP/IP configuration settings.
How To Install and Configure a DHCP Server in an Active Directory Domain in Windows Server 2003
This step-by-step article describes how to build and configure a new Windows Server 2003-based Dynamic Host Configuration Protocol (DHCP) server in a Windows Server 2003 Active Directory domain.
HOW TO: Configure Packet Filter Support for PPTP VPN Clients in Windows Server 2003
This article describes how to configure packet filter support for PPTP VPN clients. The Windows Server 2003 Routing and Remote Access service supports virtual private networking (VPN).
HOW TO: Provide Secure Point-to-Point Communications Across a Private Network or the Internet in Windows Server 2003
This step-by-step article describes how to install and configure a virtual private network (VPN) to provide secure point-to-point communications across a private network or the Internet.
HOW TO: Prevent Mail Relay in the IIS SMTP Virtual Server in Windows Server 2003
This step-by-step article describes how to prevent mail relays for an Internet Information Services (IIS) Simple Mail Transport Protocol (SMTP) virtual server.

How to Configure IIS to Host my Web Page

No comments: