Transcript Resolution Methods

Name Resolution
Presented
By
Tom Battaglia
Thomas Text
4 Section presentation

Section 1 - Resolution Methods Defined

Section 2 - Microsoft Name Resolution

Section 3 - The OSI Model

Section 4 - Troubleshooting
Thomas Text
Section 1 of 4
Resolution Methods Defined
Thomas Text
Resolution Methods

What is Name resolution

Computers communicate using IP’s

People communicate using computer names

Name resolution is a result of a client query to
get an IP address for a computer name

“Name Server” - The server that can hand out
an IP after a query for one is made
NOTE: If a client uses an IP to communicate the
Name Server is not necessary
Thomas Text
Resolution Methods

Types of Resolution Methods
Broadcast for NetBIOS Name
 WINS - Windows Internet Name Server
 DNS - Domain Name Server
 DDNS - Dynamic Domain Name Server


Node Type Resolution of Microsoft clients
 B-node / P-node / M-node / H-node
 LMHOST / HOST
Thomas Text
Broadcast for
NetBIOS "Short" Name
Thomas Text
Resolution Methods Defined

Broadcast - Characteristics

Routers do not forward Broadcast requests off
of the subnet

Only NetBIOS "Short"names can be resolved
on the local subnet

Every Client on the subnet processes
Broadcast packets
Thomas Text
Windows Internet Name Service
(WINS)
Note: Microsoft Windows Clients Only
Thomas Text
Resolution Methods Defined
WINS

WINS - Server Characteristics

Resolves NetBIOS "Short" Names only
• i.e. Batman01

Client updates dynamic database on WINS
server during startup or Nbtstat -RR

Admin can add static entries to WINS

ONLY Services are registered in WINS

WINS Servers exchange entries by being
"Push/Pull" partners
Thomas Text
Resolution Methods Defined
WINS

WINS - Client Characteristics

* Client DOES NOT use secondary unless
primary WINS server is down

To resolve a name to an IP the client must be
 using a WINS server that the destination
server registered with
OR

The clients WINS server is a "Push/Pull"
partner of the destinations WINS server
* NT4 Only. W2K will use Secondary after a delay.
Thomas Text
Resolution Methods Defined
WINS

WINS – Server Locations
WINS Servers
AUSWINSRR201
143.166.233.252
W2K
NASHVILLE
AUSTIN
AUSWINSPS201
143.166.140.96
"NEW W2K"
BNAWINSEG101
163.244.252.252
W2K
BNADHCPCORP01
163.244.252.244
W2K
APCC2
AUSWINSBT101
143.166.33.148
W2K
AUSWINSBT102
143.166.98.24
"PoleStar1
PENMDSWINS01
163.244.112.253
W2K
APCC1
Japan
TK-BDC1
163.244.85.168
NT4
PENWINSD1O10
163.244.112.26
W2K
JPWINSDC101
163.244.85.166
W2K
IEBRYWINS01
163.244.76.31
NT4
PENWINSD101
163.244.101.26
W2K
EMEA
IELIMWINS01
163.244.4.32
NT4
PENWINSD102
163.244.101.27
W2K
CHINA
EUROPEWINSNT2
163.244.79.191
NT4
CN-WINS1
163.244.235.26
NT4
Thomas Text
Resolution Methods Defined
WINS

WINS – MMC Example
Thomas Text
Resolution Methods Defined
WINS

WINS – Unique Type Examples

WINS Entry Type
[00h] Computer Name
Service Registered
Workstation Service

[03h] Computer Name
Messenger Service for Computer

[20h] Computer Name
File Server Service

[BEh] Computer Name
Network Monitoring Agent Service

[03h] User Name
Messenger Service for the logged on user

[1Bh] Domain Name
Domain Master Browser Service – PDC

[1Dh] Domain Name
Subnet Master Browser Service
Thomas Text
Resolution Methods Defined
WINS

WINS – Group Type Examples

WINS Entry Type
[00h] Domain Name
Service Registered
Workstation Service Receives Browser
Broadcasts

[1Ch] Domain Name
Domain Controllers

[1Eh] Domain Name
Used by Browsers for Elections

[01h] --_MSBROWSE_
Registered by Subnet Master Browser
Returned to clients after Query
1 PDC
24 BDCs
Thomas Text
Domain Name Service
(DNS)
Thomas Text
Resolution Methods Defined
DNS

DNS - Server Characteristics
Resolves Fully Qualified Domain Names
"FQDN"
• i.e. Batman01.us.dell.com.
 Integrated Microsoft and UNIX Servers


All Registrations are Statically Entered

Provides Forward Lookup - Name to IP

Provides Reverse Lookup - IP to Name
Thomas Text
Resolution Methods Defined
DNS

DNS - Client Characteristics

The Client uses Domain Suffixes to Lookup
Names
• i.e. "us.dell.com"
• i.e. "dell.com"

Client WILL use Secondary if Name can not
be Found on Primary DNS Server
Thomas Text
Resolution Methods Defined
DNS

DNS – Domain Suffixes
Primary DNS Suffix NT4 Legacy
dell.com
Root Domain
us.dell.com
Child Domain
us.dell.com
Austin
N/A
Brazil
ca.dell.com
Canada
N/A
Chile
N/A
Columbia
mx.dell.com
Mexico
N/A
Nashville
N/A
San Jose
my.dell.com
APCC
NT4
Client / Server
Setup
Austin Area
NON W2K
us.dell.com
dell.com
aus.amer.dell.com
amer.dell.com
bna.amer.dell.com
sjc.amer.dell.com
Thomas Text
Resolution Methods Defined
DNS

DNS – Forward Lookup MMC Example
IP Address
Host Names
IP Alias
Thomas Text
Resolution Methods Defined
DNS

DNS – Forward Lookup Unix Example
IP Address
Host Names
IP Alias
Thomas Text
Resolution Methods Defined
DNS

DNS – Reverse lookup MMC Example
Host Names
IP - First Octet
Thomas Text
Resolution Methods Defined
DNS

DNS – Reverse lookup Unix Example
Filename
Host Names
IP - First Octet
Thomas Text
Dynamic Domain Name Service
(DDNS)
Thomas Text
Resolution Methods Defined
DDNS

DDNS - Server Characteristics
Resolves Fully Qualified Domain Names
"FQDN"
• i.e. Batman01.aus.amer.dell.com.
 ONLY Microsoft W2K servers


Some Registrations are Statically Entered

Provides Forward Lookup - Name to IP

Provides Reverse Lookup - IP to Name

Proxy Lookup to the WINS Server
Thomas Text
Resolution Methods Defined
DDNS

DDNS - Client Characteristics

The Client uses Domain Suffixes to Lookup
Names
• i.e. "aus.amer.dell.com"
• i.e. "amer.dell.com"
Client WILL use Secondary if Name can not
be Found on Primary DNS Server
 Registrations are Dynamically Entered when
the W2K client uses a DDNS server

Thomas Text
Resolution Methods Defined
DDNS

DDNS – Domain Suffixes
Primary DNS Suffix W2K
dell.com
Root Domain
amer.dell.com
Child Domain
aus.amer.dell.com
Austin
poa.amer.dell.com
Brazil
yyz.amer.dell.com
Canada
bog.amer.dell.com
Chile
sgl.amer.dell.com
Columbia
mex.amer.dell.com
Mexico
bna.amer.dell.com
Nashville
sjc.amer.dell.com
San Jose
mfg.apcc.my.dell.com
mds.my.dell.com
APCC
APCC2
W2K
Client / Server
Setup
Austin Area
W2K
aus.amer.dell.com
us.dell.com
amer.dell.com
dell.com
bna.amer.dell.com
sjc.amer.dell.com
Thomas Text
Resolution Methods Defined
DDNS

DDNS – Forward Lookup MMC Example
IP Address
Host Names
Thomas Text
Resolution Methods Defined
DDNS

DDNS – Reverse lookup MMC Example

Not currently implemented at Dell on the W2K
DDNS platform
Thomas Text
Section 2 of 4
Microsoft Name Resolution
Thomas Text
Microsoft Name Resolution

Part 1 - Resolution Methods
B-node / P-node / M-node / H-node
 LMHOST File
 HOST File


Part 2 - Combined Resolution Methods
NetBIOS
 DNS

Thomas Text
Part 1
Resolution Methods
Thomas Text
Microsoft Name Resolution

B-Node - Characteristics

Uses Broadcast NetBIOS Name Queries for
Name Registration and Resolution

B-Node Limitations:
(1) Broadcasts Disturb every node on the
Network
(2) Routers Typically do not Forward
Broadcasts, so only NetBIOS Names on
the Local Network can be Resolved
Thomas Text
Microsoft Name Resolution

P-Node - Characteristics

Uses NetBIOS Name Server (NBNS)
- Typically a WINS Server

P-Node Limitations:
(1) If the Server is not Registered with
WINS the Client can not Resolve it
(2) If the NBNS is "Down" the Client May
not Resolve or will use the Secondary with
Degraded Results
Thomas Text
Microsoft Name Resolution

M-Node - Characteristics

Uses B-Node First

Uses P-Node if B-Node does not Resolve

M-Node Limitations:
(1) Broadcasts Disturb Every Node on the
Network
(2) If the NBNS is "Down" the Client May
not Resolve or will use the Secondary with
Degraded Results
Thomas Text
Microsoft Name Resolution

H-Node - Characteristics

Uses P-Node First

Uses B-Node if B-Node does not Resolve

H-Node Advantages:
(1) It Does Not Use Broadcasts First
(2) It Will Resolve Faster Using WINS and
cut down on Network Traffic
NOTE: This is the method Microsoft uses for all
their Windows platforms
Thomas Text
Microsoft Name Resolution

LMHOST File - Characteristics

Used to resolve NetBIOS "Short" Names

Can have Entries Cached from file

Located in [%systemroot%\system32\drivers\etc]

LMHOST File Limitations:
(1) Can hold only 128 entries
(2) If a Name Changes all LMHOST Files
Need to be Updated
Thomas Text
Microsoft Name Resolution

LMHOST File Example
LMHOST File - No Extension
LMHOST Sample File
Examples
Thomas Text
Microsoft Name Resolution

HOST File - Characteristics

Used to resolve FQDN Names

Can have Entries Cached from file

Located in [%systemroot%\system32\drivers\etc]

HOST File Limitations:
(1) If a Name Changes all HOST Files Need
to be Updated
Thomas Text
Microsoft Name Resolution

HOST File Example
HOST File - No Extension
Examples
Thomas Text
Part 2
Combined Resolution Methods
Thomas Text
Microsoft Name Resolution

All Microsoft Platforms - NetBIOS

Uses B-Node if no WINS Server Specified

Uses H-Node Resolution if a WINS Server is
Specified

If System Fails to Register with WINS it will
Result in B-Node until it can Contact the
WINS Server

Some Commands - Net View and Nbtstat
Thomas Text
Microsoft Name Resolution
M-Node
P-Node
M-Node
H-Node
LMHOST
Cache
LMHOST
Cache
LMHOST
Cache
LMHOST
Cache
Broadcast
WINS
WINS
WINS
Broadcast
LMHOST
File
LMHOST
File
LMHOST
File
If Configured for
"DNS for WINS
Resolution (NT4)"
If Configured for
"DNS for WINS
Resolution (NT4)"
HOST
File
HOST
File
DNS Server
DNS Server
Broadcast
LMHOST
File
NetBIOS
Resolution
Thomas Text
Microsoft Name Resolution

H-Node
Cache
WINS
Broadcast
LMHOST File
HOST File
DNS Server
Time Out
An example of name resolution would be like
calling information to get the # - (IP Address)
 Try to remember the #
 Call information to get a # for a name
 The operator can put your call through
 If the # is unlisted you might need to go in
your front yard and call their name
 Check the Counter for Pieces of Paper
 You might check your personal phone list
 Look it up in the phone book (FQDN)
 Give up and go shopping
Thomas Text
Microsoft Name Resolution

All Microsoft Platforms - DNS / DDNS
Client will look on Server and Query Using
the Domain Suffixes
 Some Commands - Ping, Ftp, and Telnet

Suffix Search
Order
DNS
Server
Thomas Text
Microsoft Name Resolution

Microsoft Reference Articles

Q105997 - Differences Between the HOSTS and LMHOSTS Files in Windows NT

Q119493 - NetBIOS over TCP-IP Name Resolution and WINS

Q120642 - TCP-IP & NBT Configuration Parameters for Windows NT and
Windows 2000

Q142042 - Description of TCP-IP Node-Type Settings in Windows 95-98

Q142309 - NetBIOS Name Resolution Using DNS and the HOSTS File

Q158474 - Windows TCP-IP Registry Entries

Q160177 - Default Node Type for Microsoft Clients

Q167640 - Automatically Changing the Node Type of a Windows NT Workstation
Thomas Text
Section 3 of 4
The OSI Model
Thomas Text
Open Systems Interconnection
(OSI) Model

OSI Characteristics
 Describes how information from a software application in
one computer moves through a network medium to a
software application in another computer

Developed by the International Organization for
Standardization (ISO) in 1984

Each layer being implemented independently enables the
solutions offered by one layer to be updated without
adversely affecting the other layers
Thomas Text
Open Systems Interconnection
(OSI) Model

OSI Characteristics
 Data Encapsulation and Decapsulation occurs as each
layer passes data up and down the stack

Layered approach for ease of Learning, Modular
Engineering, Interoperability and Eases Standards
Development

Ethernet = Frames

TCP/IP = Packets
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7 — Application layer
 Layer 6 — Presentation layer
 Layer 5 — Session layer
 Layer 4 — Transport layer
 Layer 3 — Network layer
 Layer 2 — Data Link layer
 Layer 1 — Physical layer

Implemented
with software
Implemented
with Software
& Hardware
Thomas Text
Open Systems Interconnection
(OSI) Model

"FYI" OSI Compared to TCP/IP Stack
OSI 7 Layers
Application
 Presentation
 Session
 Transport
 Network
 Data Link
 Physical

TCP/IP 4 Layers

Application
Transport
 Internet
 Interface

Thomas Text
Open Systems Interconnection
(OSI) Model
Each layer communicates with three other OSI layers:
1. The layer directly above it,
2. The layer directly below it
3. Its peer layer in other networked device
Application
 Presentation
 Session
 Transport
 Network
 Data Link
 Physical

Application
 Presentation
 Session
 Transport
 Network
 Data Link
 Physical

Upper Layer
"Service User"
Peer-to-Peer
Communication
Protocol Data Units
(PDU)
Lower Layer
"Service Provider"
Thomas Text
Open Systems Interconnection
(OSI) Model
Application
 Layer 6
 Layer 5
 Layer 4
 Layer 3
 Layer 2
 Layer 1





Interface to Application
Interface to User
UDP Application examples
 DHCP
 BOOTP
 TFTP
TCP Application examples
 HTTP
 FTP
 TELNET
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Presentation
 Layer 5
 Layer 4
 Layer 3
 Layer 2
 Layer 1







"Translator"
Encryption
Decryption
Compression
Decompression
Architecture Independent data
transfer format. i.e.
 MPEG
 Gif
 Jpeg
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Session
 Layer 4
 Layer 3
 Layer 2
 Layer 1





"Coordinator"
Manage User Sessions
 Establish Connection
 Manage Connection
 Terminate Connection
Report upper layer errors
Protocols
 AppleTalk
 Session Control Protocol
 DECnet Phase 5
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Layer 5
 Transport
 Layer 3
 Layer 2
 Layer 1







"Segmenter"
Reliable Packet Delivery
Flow Control
Multiplexing
Error Checking
Protocols Used
 TCP
 UDP
 SPX
 NetBEUI
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Layer 5
 Layer 4
 Network
 Layer 2
 Layer 1









"Packet" (Data gram)
Logical Addressing
Path Determination (Routing)
Connectionless
Best-Effort-Delivery
Address Res. Protocol -ARP
 IP to MAC
Routed Protocols
 IP / IPX / ICMP
Routing Protocols
 OSPF / RIP / BGP
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Layer 5
 Layer 4
 Layer 3
 Data Link
 Layer 1








"Frame"
Switches Operate Here
All devices talk MAC
Header Contains MAC Address
Error Notification
Network Topology Defined
Flow Control
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Layer 5
 Layer 4
 Layer 3
 Data Link
 Layer 1


Data Link Layer Sub layers
 Logical Link Control - LLC
 802.2
 Connectionless &
Connection Oriented
 Media Access Control - MAC
 Manage protocol
access to the physical
layer
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Layer 5
 Layer 4
 Layer 3
 Data Link
 Layer 1

Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Layer 5
 Layer 4
 Layer 3
 Layer 2
 Physical








"Link"
Changes data to electrical
impulses
Transmits "Bits" onto the Wire
Removes "Bits" off the Wire
Physical error checking
Does not add or take away
from the Frame
Concerned with Physical
protocol and not Data Protocol
Thomas Text
Open Systems Interconnection
(OSI) Model
Layer 7
 Layer 6
 Layer 5
 Layer 4
 Layer 3
 Layer 2
 Physical



Maintains the Physical Link
Defines the physical medium
 Voltage levels &
timings
 Data Rates
 Transmission
Distance
 Connectors
 Cables
Thomas Text
Section 4 of 4
Troubleshooting
Thomas Text
Troubleshooting

Part 1 - Basic Network Troubleshooting

Part 2 - NetBIOS Troubleshooting


Broadcast / WINS / LMHOST File
Part 3 - FQDN Troubleshooting

DNS / DDNS / Host File
Thomas Text
Part 1
Basic Network Troubleshooting
Thomas Text
Troubleshooting
Basics

Client Considerations
 ONLY GATHER FACTS………..
•

Is it "Slow" or "Not Working"?
•

They Say "Last Week" …… It's Really "Never"
What Changed?
•

They Say "No One" ………It's Really "Everyone Can"
When Did it Work Last?
•

They Say "It's Dead" ……… It's Really been "Slow" Once Today
Can Other Clients get to the Server?
•

Don't trust the end user to evaluate.
They Say "Nothing" ……… It's Really their Kids Game They Installed
Is the Client Properly Configured?
•
They Say "Yes" ……….. They Don't know what a Computer is
Thomas Text
Troubleshooting
Basics

Server Considerations
 ONLY GATHER FACTS………..

Is it Static or DHCP?

Can the Server Resolve Names?

When Did it Work Last?

What Changed?

Is the Server Properly Configured?
Thomas Text
Troubleshooting
Basics

Parts to Troubleshoot


Separate the network from the Servers

Cables, Switches and Routers are the Net

Computers are the Clients and Servers

If the Network has a Problem Usually
Several People are Affected
Check the Physical Layer

Is it the Correct Cable

Is there a Link Light

Does another Computer work in the port
Thomas Text
Troubleshooting
Basics

Parts to Troubleshoot

Check the Computer Configuration
•
http://inside.us.dell.com/it/is/network/
Configuration Docs
Thomas Text
Troubleshooting
Basics

Parts to Troubleshoot


Check the Computer Configuration
Set CLASSID for W2K DHCP Clients
Capital W2K
Thomas Text
Troubleshooting
Basics

Parts to Troubleshoot

Check the Computer Configuration
Domain Suffixes
Subnet Mask
WINS & DNS
Servers
Class ID
Thomas Text
Troubleshooting
Basics

Remove Name Resolution From The Test






PING Remote by IP
Ping Gateway by IP
Ping Loopback (127.0.0.1)
Map Drive by IP i.e. net use * \\10.180.12.26\c$
Tracert to IP
i.e. tracert 10.180.12.26
"Net View" to IP i.e. net view \\10.180.12.26
NOTE: Resolve ALL IP Issues Prior to
Troubleshooting Name Resolution Issues
Thomas Text
Troubleshooting
Basics

PING IP Example
Try to Resolve Name
Name Resolved
Thomas Text
Troubleshooting
Basics

Tracert Example
Found
Not Found
Thomas Text
Troubleshooting
Basics

Netstat Syntax
"/?" Display Help
Switches
Thomas Text
Troubleshooting
Basics

Netstat -a Example
Port State
Protocol
Thomas Text
Troubleshooting
Basics

Netstat -n Example
Port State
Protocol
Thomas Text
Troubleshooting
Basics

Netstat -r Example
Default Gateway
Remote
Thomas Text
Troubleshooting
Basics

Netstat -s Example
Is Data Moving ?
Thomas Text
Part 2
NetBIOS Troubleshooting
Thomas Text
Troubleshooting
NBNS (WINS)

Client Considerations

Can Not Login to the Domain
•

Can Not Map a Drive by Name
•

"No Domain Controller Found"
"Host Name Not Found"
Can Not "Net View" a computer
•
"Host Name Not Found"

What WINS Server are they using

Can Other Computers Map Drives by Name

Does Not Need to Register with WINS to
Resolve
Thomas Text
Troubleshooting
NBNS (WINS)

Server Considerations

Are all the Services Registered in WINS?
•

The Name Resolution is up to the Client if all the
Server Services are Registered in WINS
If the Server is down several people are
having the SAME problem(s)
Thomas Text
Troubleshooting
NBNS (WINS)

Add Name Resolution To The Test

"Nbtstat" to "Short Name"
•

"Net View" to "Short Name"
•

i.e. net view \\ausgnsnpt01
Map Drive by "Short Name"
•

i.e. nbtstat -a \\ausgnsnpt01
i.e. net use * \\ausgnsnpt01\c$
PING Remote by "Short Name"
•
i.e. Ping ausgnsnpt01
Thomas Text
Troubleshooting
NBNS (WINS)

Nbtstat Syntax
"/?" Display Help
Switches
Thomas Text
Troubleshooting
NBNS (WINS)

Nbtstat -a Example
"-a" Remote
Services & MAC
"-n" Local
Services NO MAC
Thomas Text
Troubleshooting
NBNS (WINS)

Nbtstat -c Example
"-c" Cache
"-r" Resolved
Thomas Text
Troubleshooting
NBNS (WINS)

Nbtstat -s and -RR Example
"-s or -S" Sessions
"-RR" ReRegister
with WINS
Thomas Text
Troubleshooting
NBNS (WINS)

Net View Syntax and Example
Show Browse List
"Short Name"
Thomas Text
Troubleshooting
NBNS (WINS)

Net Use Syntax and Example
Map next Drive
Letter
Ask for Password
Delete Map
Thomas Text
Troubleshooting
NBNS (WINS)

PING Example
Note: PING is a DNS Command for FQDN but can be
used to troubleshoot Net BIOS
FQDN Name Resolved
by DNS
"Short Name" Resolved
by Broadcast or WINS
Thomas Text
Troubleshooting
NBNS (WINS)

LMHOST File
Clear the LMHOST file
if not needed or you are
troubleshooting
Thomas Text
Part 3
FQDN Troubleshooting
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

Client Considerations

Does the App use FQDNs?

Is the Domain Suffix Correct?

Check for the correct Name Server

Is the IP Address in DNS or DDNS
•
•

us.dell.com - Legacy
aus.amer.dell.com - W2K
Can Not Map a Drive by FQDN
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

Server Considerations

Is the Name in DNS or DDNS?
•

The Name Resolution is up to the Client if the server
is in DNS or DDNS it has met the minimum
requirements
If the Server is down several people are
having the SAME problem(s)
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

NSLookup Syntax
Show Commands
Commands
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

NSLookup Example
Authoritative
amer.dell.com
DDNS Server
Query Returned
Non-Authoritative
amer.dell.com
DDNS Server
Query Returned
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

NSLookup Example
Non-Authoritative
us.dell.com
DDNS Server
Query Returned
Query Returned
No DNS Entry
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

PING Syntax
Show Syntax
Switches
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

PING Example
 PING Loop Back Address
• TCP/IP is Installed Properly
Loop Back
Address
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

PING Example
Domain Suffix Search
Order
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

PING Example
Domain Suffix Search
Order
Ping Short Name
WINS Responded with
"Short Name"
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

PING Example
Domain Suffix Search
Order
Ping Short Name
DDNS Responded with
FQDN
Thomas Text
Troubleshooting
DNS/DDNS (FQDN)

PING Example
 PING Loop Back Name in Host File
• TCP/IP is Installed Properly
• Host File is Working
Loop Back Name
"Localhost"
Thomas Text
Name Resolution
Presented
By
Tom Battaglia
Thomas Text