New Posts  All Forums:Forum Nav:

My NetBIOS notes

post #1 of 4
Thread Starter 
Hi All,

At the moment I am compiling some extra notes about networking, particularly in a Windows environment. Was hoping you could check whether I am right and kindly point out any errors in my understanding that you see, as I don't know anyone else who can help me on this. That would be most helpful and appreciated.

Ok, so this is what I've got so far:


NETWORKING WITH MICROSOFT WINDOWS


MS Windows sits at the Application Layer of the OSI reference model. However, built into the OS are a number of lower level protocols, including the TCP/IP suite.

Once a common TCP/IP link has been successfully established across all host on a LAN, each host further needs to setup a common WORKGROUP name within the MS Windows operating system (OS). All host configured with the same Workgroup name are said to belong to the same Windows domain.

Tradionally, NetBIOS has been the primary Application layer protocol utilised by MS Windows to establish the sharing of resources (file and printer sharing) across the LAN.

In a simplified model (not factoring individual administrative security requirements), NetBIOS determines which users to grant or deny the sharing of resources by cross - referencing the Workgroup name of the two communicating host to see if there is a match. Users within the same Workgroup domain are granted access, and those outside are denied.
Meh, good enough
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 955 C3 @ 3.8GHz Gigabyte GA-880GA-UD3H ASUS 7970 Direct CU II G.Skill F3-17600CL7D-4GBPIS 
Hard DriveOSPowerCase
WDC WD6000HLHX Windows 7 Home Premium 64-bit Antec True Power 750W Cooler Master Elite 370 
Audio
ASUS Xonar DG 
  hide details  
Reply
Meh, good enough
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 955 C3 @ 3.8GHz Gigabyte GA-880GA-UD3H ASUS 7970 Direct CU II G.Skill F3-17600CL7D-4GBPIS 
Hard DriveOSPowerCase
WDC WD6000HLHX Windows 7 Home Premium 64-bit Antec True Power 750W Cooler Master Elite 370 
Audio
ASUS Xonar DG 
  hide details  
Reply
post #2 of 4
Thread Starter 
Ok, apparently I'm slightly off. It seems NetBIOS is more commonly associated with OSI reference model Session layer. So, I've made some slight modifications....


MS Windows sits at the Application Layer of the OSI reference model. However, built into the OS are a number of lower level protocols, including the TCP/IP suite and NetBIOS.

Once a common TCP/IP link has been successfully established across all host on a LAN, each host further needs to setup a common WORKGROUP name within the MS Windows operating system (OS). All host configured with the same Workgroup name are said to belong to the same Windows domain.

Tradionally, NetBIOS has been the primary Session layer protocol utilised by MS Windows to help establish the sharing of Application layer resources (file and printer sharing) across the LAN. As a Session layer protocol, its task is to automatically setup and maintain a session between the various host within the Windows domain. Each session is kept track of through a port number. With a session successfully established, the hosts can then communicate together at the Application layer.

In a very simplified model without factoring admistrative security, NetBIOS determines which users to establish sessions with and thus grant or deny the sharing of resources by cross - referencing the Workgroup name of the two communicating host to see if there is a match. Users within the same Workgroup domain are granted access, and those outside are denied.



I'm am 85% sure this is correct. I kinda wanna get a move on with my notes so I will be writing this copy up in my study notes. Hope it may be of some help to someone else curious about this same topic.

Here's a few helpful websites I found too. I can't confirm their sources, but they all seem to be on the right track


http://www.networktutorials.info/osi_layers.html

http://www.lex-con.com/osimodel.htm
Meh, good enough
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 955 C3 @ 3.8GHz Gigabyte GA-880GA-UD3H ASUS 7970 Direct CU II G.Skill F3-17600CL7D-4GBPIS 
Hard DriveOSPowerCase
WDC WD6000HLHX Windows 7 Home Premium 64-bit Antec True Power 750W Cooler Master Elite 370 
Audio
ASUS Xonar DG 
  hide details  
Reply
Meh, good enough
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 955 C3 @ 3.8GHz Gigabyte GA-880GA-UD3H ASUS 7970 Direct CU II G.Skill F3-17600CL7D-4GBPIS 
Hard DriveOSPowerCase
WDC WD6000HLHX Windows 7 Home Premium 64-bit Antec True Power 750W Cooler Master Elite 370 
Audio
ASUS Xonar DG 
  hide details  
Reply
post #3 of 4
Netbios is useful in a DHCP environment where you still you want access to computers that changes IP often, but in larger networks or ones where static IPs are implemented, it isn't really practical. I wouldn't call it a packet storm, but on a network with many machines, accessing a computer with netbios names can take forever.

You can think of it as IP broadcasted DNS-ish kind of thing. It simply resolves an address with a hostname. I do believe it is a session layer protocol.

Are you writing these notes for your own personal pleasure or for a class?
Indigo Hammer
(5 items)
 
Blue Danube
(7 items)
 
 
CPUGraphicsOSKeyboard
Core i5-4250U Intel HD5000 OS X 10.8.4 Filco Minila Air - MX Blue 
Audio
TCA Gizmo > Axiom Audio M2ti 
  hide details  
Reply
Indigo Hammer
(5 items)
 
Blue Danube
(7 items)
 
 
CPUGraphicsOSKeyboard
Core i5-4250U Intel HD5000 OS X 10.8.4 Filco Minila Air - MX Blue 
Audio
TCA Gizmo > Axiom Audio M2ti 
  hide details  
Reply
post #4 of 4
Thread Starter 
Hi max302, thanks for the reply !

Its the NetBIOS protocol however that seeks out and finds what 'WORKGROUP' a MS Windows host is configured for, right? And you're dead right about it also finding and grabbing the configured hostname. I'll need to scribble that into my notes

Yes, the notes are just for my own personal gratification. I did a compressed Cisco networking (CCNA) course a few years ago, however the course really never touched on networking in a Windows environment.

So am just trying to understand the mechanics of how MS Windows networks between other MS Windows hosts. The NetBIOS and WINS protocols were sadly complete mysteries to me, so have been trying to educate myself about it all .
Meh, good enough
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 955 C3 @ 3.8GHz Gigabyte GA-880GA-UD3H ASUS 7970 Direct CU II G.Skill F3-17600CL7D-4GBPIS 
Hard DriveOSPowerCase
WDC WD6000HLHX Windows 7 Home Premium 64-bit Antec True Power 750W Cooler Master Elite 370 
Audio
ASUS Xonar DG 
  hide details  
Reply
Meh, good enough
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 955 C3 @ 3.8GHz Gigabyte GA-880GA-UD3H ASUS 7970 Direct CU II G.Skill F3-17600CL7D-4GBPIS 
Hard DriveOSPowerCase
WDC WD6000HLHX Windows 7 Home Premium 64-bit Antec True Power 750W Cooler Master Elite 370 
Audio
ASUS Xonar DG 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Networking & Security