WintelGuide has now moved on to new home with new address with more information
Click on above link to stay tunned.
Thanks,
Winteladmin.com
You can use Computer Management to track all connections to shared resources on a Windows Server 2008 R2 system. Whenever a user or computer connects to a shared resource, Windows Server 2008 R2 lists a connection in the Sessions node.
To view connections to shared resources, type net session at a command prompt or follow these steps:
1. In Computer Management, connect to the computer on which you created the shared resource.
2. In the console tree, expand System Tools, expand Shared Folders, and then select Sessions. You can now view connections to shares for users and computers.
The columns for the Sessions node provide the following important information about user and computer connections:
User The names of users or computers connected to shared resources. Computer names are shown with a $ suffix to differentiate them from users.
Computer The name of the computer being used.
Type The type of network connection being used.
# Open Files The number of files the user is actively working with. For more detailed information, access the Open Files node.
Connected Time The time that has elapsed since the connection was established.
Idle Time The time that has elapsed since the connection was last used.
Guest Whether the user is logged on as a guest.
Windows contains an assortment of utilities you can use to diagnose, monitor, and repair network connections. Here’s an overview of the key tools you’ll find in Windows Operating System and what they’re used for.
Get MAC Address (Getmac.exe)
Discovers the Media Access Control (MAC) address, and lists associated network protocols for all network cards in a computer, either locally or across a network.
Hostname (Hostname.exe)
Displays the host name of the current computer.
IP Configuration Utility (Ipconfig.exe)
Displays all current TCP/IP network configuration values, and refreshes DHCP and DNS settings.
Name Server Lookup (Nslookup.exe)
Displays information about Domain Name System records for specific IP addresses and/or host names so that you can troubleshoot DNS problems.
Net services commands (Net.exe)
Performs a broad range of network tasks; type net with no parameters to see a full list of available command-line options.
Netstat (Netstat.exe)
Displays active TCP connections, ports on which the computer is listening, Ethernet statistics, the IP routing table, and IPv4/IPv6 statistics.
Network Command Shell (Netsh.exe)
Displays or modifies the network configuration of a local or remote computer that is currently running; this command-line scripting utility has a huge number of options, which are fully detailed in Help.
PathPing (Pathping.exe)
Combines functions of Traceroute and Ping to identify problems at a router or network link.
TCP/IP NetBIOS Information (Nbtstat.exe)
Displays statistics for NetBIOS over TCP/IP (NetBT) protocol, NetBIOS name tables for both the local computer and remote computers, and the NetBIOS name cache.
TCP/IP Ping (Ping.exe)
Verifies IP-level connectivity to another internet address by sending ICMP packets and measuring response time in milliseconds.
TCP/IP Route (Route.exe)
Displays and modifies entries in the local IP routing table.
TCP/IP Traceroute (Tracert.exe)
Determines the path to an internet address and lists the time required to reach each hop; useful for troubleshooting connectivity problems on specific network segments.
TCP is a connection oriented protocol, which means that everytime a packet is sent say from host A to B, we will get an acknowledgement. Whereas UDP on the other hand, is a connection less protocol.
Where will it be used : TCP -> Say you have a file transfer and you need to ensure that the file reaches intact, and time is not a factor, in such a case we can use TCP.
UDP-> Media Streaming, question is say you are watching a movie…would you prefer that your movie comes..perfectly….but u need to wait a long time before you see the next frame ?..or would you prefer the movie to keep streaming…Yes…The second option is definely better….This is when we need UDP
ARP: Stands for Address Resolution Protocol…whenever a request is sent by a node on one network to the node on another network the Physical address(MAC) is required and for this the IP address need to be flow over the network..whenver a router with that network (IP) gets the msg. the required MAC address is sent through the network this process of converting the IP address to MAC address is Called ARP..and the reverse thats the convertion of the Mac address to the IP address is called RARP ( Reverse Address Resolution Protocol)
Windows Administrators Complete Blog 