Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network...

7
Microsoft enterprise concepts

Transcript of Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network...

Page 1: Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network Adapter Card Drivers NDIS InterfaceStreams Transport Protocols.

Microsoft enterprise concepts

Page 2: Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network Adapter Card Drivers NDIS InterfaceStreams Transport Protocols.

NT Layered Network Architecture

Network Interface Card

Network Adapter Card Drivers

NDIS Interface Streams

Streams

Transport Protocols

Transport Driver Interface

NetBIOS driver

Redirectors Servers WinSock driver

1. Physical

2. Data Link

3. Network

MAC

LLC

4. Transport

5. Session

6. Presentation

7. Application

Kernel Mode

User Mode

Page 3: Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network Adapter Card Drivers NDIS InterfaceStreams Transport Protocols.

Some basic concepts

NDIS Interface: Network Driver Specification Interface, wraps NIC drivers and allow communication with multiple protocols, binds a NIC to a protocol.

Streams: multiple channels allowing broader bandwidth for data transfer, envelop the protocols.

Transport Driver Interface: allows software drivers (server, redirector, etc) to communicate with protocols.

Redirectors: software in WS that redirect network drives, printers requests to network I/O requests.

Servers: software that allows a device to accept requests from other devices.

Page 4: Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network Adapter Card Drivers NDIS InterfaceStreams Transport Protocols.

Standard NT protocols

NetBEUI - NetBIOS Extended User Interface, “native” Windows protocol, not routable.

TCP/IP - implemented through WinSock, routable, supports SNMP, DHCP, WINS.

NWLink (IPX/SPX) - used to connect to Novell NetWare, just a protocol, not access.

DLC - Data Link Control, used to connect to IBM mainframes and HP printers directly connected to a network (server).

Page 5: Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network Adapter Card Drivers NDIS InterfaceStreams Transport Protocols.

Network Resource Access

UNC - Universal Naming Convention– machine name: \\mname <= 15 digits– share name: \sname <= 12 digits– example: \\AL200\HP6– sharing: net share public= c:\temp– using: net use lpt2: \\Al200\public

– also graphical

Master Browsers - allow to see what resources are available– Win 95/NT use Network Neighborhood

MUP driver - Multiple Universal Naming Convention Provider

Page 6: Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network Adapter Card Drivers NDIS InterfaceStreams Transport Protocols.

Workgroups

Peer to Peer– a machine joins a group by declaring (Control Panel)

– group names <= 15 digits

– servers: DOS with add on, Windows for Workgroups, Windows 95, NT WS and Server.

– Low security for shares, with one password for a resource, all can see share names, but in NT.

NT client-server– local and global (more in Domain)

– peer-to-peer and guest, should not be allowed

– shares require username and password

Page 7: Microsoft enterprise concepts. NT Layered Network Architecture Network Interface Card Network Adapter Card Drivers NDIS InterfaceStreams Transport Protocols.

Domain

Concept: a group of NT machines that share “a security server” - the primary domain controller (PDC VS BDCs)– Windows for Workgroups and Windows 95 can join by selecting as workgroup

name the domain name– Users with Windows 95 clients can log on NT server net similarly to NT

workstations.– user name <= 20 digits, password <= 14 digits– users have permissions (access) and rights (do something), groups– SAM - Security Account Manager, keep user information

Trust relationships: allow an user to be part of more than one domain.– If A trusts C, users in C can access resources in A (one-way)– two-way trusts : users of both both can access the other