Troubleshooting hardware addresses by using arp
The Address Resolution Protocol (ARP) allows a host to find the media access
control address of a host on the same physical network, given the IP address of
the host. To make ARP efficient, each computer caches IP–to–media access
control address mappings to eliminate repetitive ARP broadcast requests.
You can use the arp command to view and modify the ARP table entries on the
local computer. The arp command is useful for viewing the ARP cache and
resolving address resolution problems.
Troubleshooting NetBIOS names by using nbtstat
NetBIOS over TCP/IP (NetBT) resolves NetBIOS names to IP addresses. TCP/IP
provides many options for NetBIOS name resolution, including local cache
lookup, WINS server query, broadcast, DNS server query, and Lmhosts and Hosts
file lookup.
Nbtstat is a useful tool for troubleshooting NetBIOS name resolution problems.
You can use the nbtstat command to remove or correct preloaded entries:
nbtstat –n displays the names that were registered locally on the system by
programs such as the server and redirector.
nbtstat –c shows the NetBIOS name cache, which contains name-to-address
mappings for other computers.
nbtstat –R purges the name cache and reloads it from the Lmhosts file.
nbtstat –RR releases NetBIOS names registered with a WINS server and then
renews their registration.
nbtstat –a name performs a NetBIOS adapter status command against the computer
specified by name. The adapter status command returns the local NetBIOS name
table for that computer plus the media access control address of the adapter.
nbtstat –S lists the current NetBIOS sessions and their status, including
statistics, as shown in the following example:
NetBIOS connection table
Local name State In/out Remote Host Input Output
------------------------------------------------------------------
CORP1 <00> Connected Out CORPSUP1<20> 6MB 5MB
CORP1 <00> Connected Out CORPPRINT<20> 108KB 116KB
CORP1 <00> Connected Out CORPSRC1<20> 299KB 19KB
CORP1 <00> Connected Out CORPEMAIL1<20> 324KB 19KB
CORP1 <03> Listening
Displaying connection statistics by using netstat
You can use the netstat command to display protocol statistics and current
TCP/IP connections. The netstat –a command displays all connections, and
netstat –r displays the route table plus active connections. The netstat –e
command displays Ethernet statistics, and netstat –s displays per-protocol
statistics. If you use netstat –n, addresses and port numbers are not converted
to names. The following shows sample output for netstat:
C:\>netstat -e
Interface Statistics
Received Sent
Bytes 3995837940 47224622
Unicast packets 120099 131015
Non-unicast packets 7579544 3823
Discards 0 0
Errors 0 0
Unknown protocols 363054211
C:\>netstat -a
--
JRS
[email protected]
Facts do not cease to exist just
because they are ignored.
On Oct 10, 2011, at 5:02 PM, DSinc wrote:
> inline........................
>
> On 10/10/2011 19:02, John Steinbruner wrote:
>> Does the printer still show in network neighborhood?
> Well it did not before, because I disabled the "NETBIOS/IP" protocol.
> I have now re-Enabled this protocol at the printer via my HTTP connection.
> I now again have the "BRN-mac addy-" icon in my network neighborhood AGAIN.
> I step forward.............. :)
>> Perhaps the master browser got reset in the power outage?
> Perhaps? But, I still do not know how to find 'WHO' the Master Browser is.
> I have read each thread about this 'mb' business and still do not know how to
> push it about; much less repair it when glitched!
>> Self test still works from the printer so we know nothing got damaged in the
>> power outage?
> Well, it does seem so; except that now WinXP does not recognize the printer's
> print
> server.
> I would so like to believe the Brother internal Print Server is sadly
> confused ATM. I can NOT
> prove-troubleshoot this........... :(
>
> The printer speaks to me via HTTP (on my OFC client) and seems to give me
> complete access to its' innards. Yes, from my client's browser HTTP
> connection to the
> printer I seem to be able to fully admin the printer and print server. I have
> only changed
> the printer's IP addy, and re-enabled the "NETBIOS/IP" protocol so far.
>
> As mentioned prior, I am still thinking about a Factory Reset.
> As mentioned prior, I am still thinking about a F/W Update/Reload.
>
> Rhetorical: Why do Printers still cause so much grief?
>
> ATM, I copy the mail. This printer is only 2 months old; so, it remains
> under the Brother
> warranty..........
> HTH,
> Duncan
>
>>
>>
