A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Performance and Maintainance of XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Tracert in XP



 
 
Thread Tools Display Modes
  #46  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

Ads
  #47  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

  #48  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

  #49  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

  #50  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

  #51  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

  #52  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

  #53  
Old April 18th 04, 01:37 PM
Wesley Vogel
external usenet poster
 
Posts: n/a
Default Tracert in XP

Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323388

To Display Connection Information by Using the Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution
problems. You can use the NBTSTAT command to remove or correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type nbtstat -n at the
command prompt, and then press ENTER. This command returns the NetBIOS local
name table. It indicates whether each name is a unique name or a group name
and whether the name is registered or unregistered on the network.

To list the contents of the NetBIOS name cache, type nbtstat -c at the
command prompt, and then press ENTER. This command shows the NetBIOS name
cache, which contains name-to-address mappings for other computers.

To clear the contents of the name cache and reload it from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type nbtstat -a
RemoteComputerName at the command prompt, and then press ENTER, where
RemoteComputerName is the NetBIOS computer name of the remote computer. The
adapter status command returns the local NetBIOS name table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type nbtstat -s at the
command prompt, and then press ENTER. This command 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
------------------------------------------------------------------
DAVEMAC1 00 Connected Out CNSSUP120 6MB 5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB 116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB 19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB 19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool, type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command, ping the desired
host using its host name.

If the ping command fails with an Unable to resolve target system name
message, verify that the host name is correct and that the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the IP address of the
computer. If pinging the IP address is successful, but pinging the computer
name is not, you might have a name resolution problem. In this case, ensure
that the computer name you are specifying can be resolved through the local
Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes of data:
====

To ping the destination ###.###.###.### and resolve ###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on the destination IP
address. If this is successful, ping displays the corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I Cannot "Ping" It by Name
If you can contact a resource by using its IP address but a PING message to
its host name does not work, the problem may be caused by a name resolution
failure, instead of by network connectivity. Make sure that the computer is
configured with the correct DNS or WINS entries, and that the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and then press ENTER.

At the command prompt, type net view \\ComputerName, and then press ENTER,
where ComputerName is the name of the computer that you want to connect to.

A list of the file and print shares on that computer is generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and you receive a
"System error has occurred" error message, follow these steps:
Verify that you typed the correct name of the remote computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways (routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work, type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command works, but the NET VIEW
\\ComputerName command does not work, the computer name may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool, type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and pecked:
No, it happens with all addresses except for servers which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

  #54  
Old April 18th 04, 01:39 PM
Lois
external usenet poster
 
Posts: n/a
Default Tracert in XP

Thanks Wesley
Nbtstat -a gives me exactly what I need.
-----Original Message-----
Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network

Connections in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-

us;323388

To Display Connection Information by Using the

Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS

name resolution
problems. You can use the NBTSTAT command to remove or

correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type

nbtstat -n at the
command prompt, and then press ENTER. This command

returns the NetBIOS local
name table. It indicates whether each name is a unique

name or a group name
and whether the name is registered or unregistered on the

network.

To list the contents of the NetBIOS name cache, type

nbtstat -c at the
command prompt, and then press ENTER. This command shows

the NetBIOS name
cache, which contains name-to-address mappings for other

computers.

To clear the contents of the name cache and reload it

from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press

ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type

nbtstat -a
RemoteComputerName at the command prompt, and then press

ENTER, where
RemoteComputerName is the NetBIOS computer name of the

remote computer. The
adapter status command returns the local NetBIOS name

table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type

nbtstat -s at the
command prompt, and then press ENTER. This command 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
-------------------------------------------------------

-----------
DAVEMAC1 00 Connected Out CNSSUP120 6MB

5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB

116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB

19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB

19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool,

type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command,

ping the desired
host using its host name.

If the ping command fails with an Unable to resolve

target system name
message, verify that the host name is correct and that

the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the

IP address of the
computer. If pinging the IP address is successful, but

pinging the computer
name is not, you might have a name resolution problem. In

this case, ensure
that the computer name you are specifying can be resolved

through the local
Hosts file, by using Domain Name System (DNS) queries, or

through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes

of data:
====

To ping the destination ###.###.###.### and resolve

###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on

the destination IP
address. If this is successful, ping displays the

corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I

Cannot "Ping" It by Name
If you can contact a resource by using its IP address but

a PING message to
its host name does not work, the problem may be caused by

a name resolution
failure, instead of by network connectivity. Make sure

that the computer is
configured with the correct DNS or WINS entries, and that

the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and

then press ENTER.

At the command prompt, type net view \\ComputerName, and

then press ENTER,
where ComputerName is the name of the computer that you

want to connect to.

A list of the file and print shares on that computer is

generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the

specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and

you receive a
"System error has occurred" error message, follow these

steps:
Verify that you typed the correct name of the remote

computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer

Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways

(routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work,

type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command

works, but the NET VIEW
\\ComputerName command does not work, the computer name

may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool,

type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and

pecked:
No, it happens with all addresses except for servers

which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

.

  #55  
Old April 18th 04, 01:39 PM
Lois
external usenet poster
 
Posts: n/a
Default Tracert in XP

Thanks Wesley
Nbtstat -a gives me exactly what I need.
-----Original Message-----
Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network

Connections in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-

us;323388

To Display Connection Information by Using the

Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS

name resolution
problems. You can use the NBTSTAT command to remove or

correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type

nbtstat -n at the
command prompt, and then press ENTER. This command

returns the NetBIOS local
name table. It indicates whether each name is a unique

name or a group name
and whether the name is registered or unregistered on the

network.

To list the contents of the NetBIOS name cache, type

nbtstat -c at the
command prompt, and then press ENTER. This command shows

the NetBIOS name
cache, which contains name-to-address mappings for other

computers.

To clear the contents of the name cache and reload it

from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press

ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type

nbtstat -a
RemoteComputerName at the command prompt, and then press

ENTER, where
RemoteComputerName is the NetBIOS computer name of the

remote computer. The
adapter status command returns the local NetBIOS name

table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type

nbtstat -s at the
command prompt, and then press ENTER. This command 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
-------------------------------------------------------

-----------
DAVEMAC1 00 Connected Out CNSSUP120 6MB

5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB

116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB

19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB

19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool,

type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command,

ping the desired
host using its host name.

If the ping command fails with an Unable to resolve

target system name
message, verify that the host name is correct and that

the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the

IP address of the
computer. If pinging the IP address is successful, but

pinging the computer
name is not, you might have a name resolution problem. In

this case, ensure
that the computer name you are specifying can be resolved

through the local
Hosts file, by using Domain Name System (DNS) queries, or

through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes

of data:
====

To ping the destination ###.###.###.### and resolve

###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on

the destination IP
address. If this is successful, ping displays the

corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I

Cannot "Ping" It by Name
If you can contact a resource by using its IP address but

a PING message to
its host name does not work, the problem may be caused by

a name resolution
failure, instead of by network connectivity. Make sure

that the computer is
configured with the correct DNS or WINS entries, and that

the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and

then press ENTER.

At the command prompt, type net view \\ComputerName, and

then press ENTER,
where ComputerName is the name of the computer that you

want to connect to.

A list of the file and print shares on that computer is

generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the

specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and

you receive a
"System error has occurred" error message, follow these

steps:
Verify that you typed the correct name of the remote

computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer

Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways

(routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work,

type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command

works, but the NET VIEW
\\ComputerName command does not work, the computer name

may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool,

type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and

pecked:
No, it happens with all addresses except for servers

which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

.

  #56  
Old April 18th 04, 01:39 PM
Lois
external usenet poster
 
Posts: n/a
Default Tracert in XP

Thanks Wesley
Nbtstat -a gives me exactly what I need.
-----Original Message-----
Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network

Connections in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-

us;323388

To Display Connection Information by Using the

Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS

name resolution
problems. You can use the NBTSTAT command to remove or

correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type

nbtstat -n at the
command prompt, and then press ENTER. This command

returns the NetBIOS local
name table. It indicates whether each name is a unique

name or a group name
and whether the name is registered or unregistered on the

network.

To list the contents of the NetBIOS name cache, type

nbtstat -c at the
command prompt, and then press ENTER. This command shows

the NetBIOS name
cache, which contains name-to-address mappings for other

computers.

To clear the contents of the name cache and reload it

from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press

ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type

nbtstat -a
RemoteComputerName at the command prompt, and then press

ENTER, where
RemoteComputerName is the NetBIOS computer name of the

remote computer. The
adapter status command returns the local NetBIOS name

table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type

nbtstat -s at the
command prompt, and then press ENTER. This command 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
-------------------------------------------------------

-----------
DAVEMAC1 00 Connected Out CNSSUP120 6MB

5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB

116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB

19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB

19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool,

type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command,

ping the desired
host using its host name.

If the ping command fails with an Unable to resolve

target system name
message, verify that the host name is correct and that

the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the

IP address of the
computer. If pinging the IP address is successful, but

pinging the computer
name is not, you might have a name resolution problem. In

this case, ensure
that the computer name you are specifying can be resolved

through the local
Hosts file, by using Domain Name System (DNS) queries, or

through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes

of data:
====

To ping the destination ###.###.###.### and resolve

###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on

the destination IP
address. If this is successful, ping displays the

corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I

Cannot "Ping" It by Name
If you can contact a resource by using its IP address but

a PING message to
its host name does not work, the problem may be caused by

a name resolution
failure, instead of by network connectivity. Make sure

that the computer is
configured with the correct DNS or WINS entries, and that

the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and

then press ENTER.

At the command prompt, type net view \\ComputerName, and

then press ENTER,
where ComputerName is the name of the computer that you

want to connect to.

A list of the file and print shares on that computer is

generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the

specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and

you receive a
"System error has occurred" error message, follow these

steps:
Verify that you typed the correct name of the remote

computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer

Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways

(routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work,

type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command

works, but the NET VIEW
\\ComputerName command does not work, the computer name

may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool,

type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and

pecked:
No, it happens with all addresses except for servers

which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

.

  #57  
Old April 18th 04, 01:39 PM
Lois
external usenet poster
 
Posts: n/a
Default Tracert in XP

Thanks Wesley
Nbtstat -a gives me exactly what I need.
-----Original Message-----
Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network

Connections in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-

us;323388

To Display Connection Information by Using the

Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS

name resolution
problems. You can use the NBTSTAT command to remove or

correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type

nbtstat -n at the
command prompt, and then press ENTER. This command

returns the NetBIOS local
name table. It indicates whether each name is a unique

name or a group name
and whether the name is registered or unregistered on the

network.

To list the contents of the NetBIOS name cache, type

nbtstat -c at the
command prompt, and then press ENTER. This command shows

the NetBIOS name
cache, which contains name-to-address mappings for other

computers.

To clear the contents of the name cache and reload it

from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press

ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type

nbtstat -a
RemoteComputerName at the command prompt, and then press

ENTER, where
RemoteComputerName is the NetBIOS computer name of the

remote computer. The
adapter status command returns the local NetBIOS name

table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type

nbtstat -s at the
command prompt, and then press ENTER. This command 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
-------------------------------------------------------

-----------
DAVEMAC1 00 Connected Out CNSSUP120 6MB

5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB

116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB

19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB

19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool,

type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command,

ping the desired
host using its host name.

If the ping command fails with an Unable to resolve

target system name
message, verify that the host name is correct and that

the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the

IP address of the
computer. If pinging the IP address is successful, but

pinging the computer
name is not, you might have a name resolution problem. In

this case, ensure
that the computer name you are specifying can be resolved

through the local
Hosts file, by using Domain Name System (DNS) queries, or

through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes

of data:
====

To ping the destination ###.###.###.### and resolve

###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on

the destination IP
address. If this is successful, ping displays the

corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I

Cannot "Ping" It by Name
If you can contact a resource by using its IP address but

a PING message to
its host name does not work, the problem may be caused by

a name resolution
failure, instead of by network connectivity. Make sure

that the computer is
configured with the correct DNS or WINS entries, and that

the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and

then press ENTER.

At the command prompt, type net view \\ComputerName, and

then press ENTER,
where ComputerName is the name of the computer that you

want to connect to.

A list of the file and print shares on that computer is

generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the

specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and

you receive a
"System error has occurred" error message, follow these

steps:
Verify that you typed the correct name of the remote

computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer

Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways

(routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work,

type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command

works, but the NET VIEW
\\ComputerName command does not work, the computer name

may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool,

type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and

pecked:
No, it happens with all addresses except for servers

which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

.

  #58  
Old April 18th 04, 01:39 PM
Lois
external usenet poster
 
Posts: n/a
Default Tracert in XP

Thanks Wesley
Nbtstat -a gives me exactly what I need.
-----Original Message-----
Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network

Connections in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-

us;323388

To Display Connection Information by Using the

Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS

name resolution
problems. You can use the NBTSTAT command to remove or

correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type

nbtstat -n at the
command prompt, and then press ENTER. This command

returns the NetBIOS local
name table. It indicates whether each name is a unique

name or a group name
and whether the name is registered or unregistered on the

network.

To list the contents of the NetBIOS name cache, type

nbtstat -c at the
command prompt, and then press ENTER. This command shows

the NetBIOS name
cache, which contains name-to-address mappings for other

computers.

To clear the contents of the name cache and reload it

from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press

ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type

nbtstat -a
RemoteComputerName at the command prompt, and then press

ENTER, where
RemoteComputerName is the NetBIOS computer name of the

remote computer. The
adapter status command returns the local NetBIOS name

table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type

nbtstat -s at the
command prompt, and then press ENTER. This command 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
-------------------------------------------------------

-----------
DAVEMAC1 00 Connected Out CNSSUP120 6MB

5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB

116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB

19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB

19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool,

type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command,

ping the desired
host using its host name.

If the ping command fails with an Unable to resolve

target system name
message, verify that the host name is correct and that

the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the

IP address of the
computer. If pinging the IP address is successful, but

pinging the computer
name is not, you might have a name resolution problem. In

this case, ensure
that the computer name you are specifying can be resolved

through the local
Hosts file, by using Domain Name System (DNS) queries, or

through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes

of data:
====

To ping the destination ###.###.###.### and resolve

###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on

the destination IP
address. If this is successful, ping displays the

corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I

Cannot "Ping" It by Name
If you can contact a resource by using its IP address but

a PING message to
its host name does not work, the problem may be caused by

a name resolution
failure, instead of by network connectivity. Make sure

that the computer is
configured with the correct DNS or WINS entries, and that

the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and

then press ENTER.

At the command prompt, type net view \\ComputerName, and

then press ENTER,
where ComputerName is the name of the computer that you

want to connect to.

A list of the file and print shares on that computer is

generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the

specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and

you receive a
"System error has occurred" error message, follow these

steps:
Verify that you typed the correct name of the remote

computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer

Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways

(routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work,

type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command

works, but the NET VIEW
\\ComputerName command does not work, the computer name

may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool,

type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and

pecked:
No, it happens with all addresses except for servers

which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

.

  #59  
Old April 18th 04, 01:39 PM
Lois
external usenet poster
 
Posts: n/a
Default Tracert in XP

Thanks Wesley
Nbtstat -a gives me exactly what I need.
-----Original Message-----
Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network

Connections in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-

us;323388

To Display Connection Information by Using the

Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS

name resolution
problems. You can use the NBTSTAT command to remove or

correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type

nbtstat -n at the
command prompt, and then press ENTER. This command

returns the NetBIOS local
name table. It indicates whether each name is a unique

name or a group name
and whether the name is registered or unregistered on the

network.

To list the contents of the NetBIOS name cache, type

nbtstat -c at the
command prompt, and then press ENTER. This command shows

the NetBIOS name
cache, which contains name-to-address mappings for other

computers.

To clear the contents of the name cache and reload it

from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press

ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type

nbtstat -a
RemoteComputerName at the command prompt, and then press

ENTER, where
RemoteComputerName is the NetBIOS computer name of the

remote computer. The
adapter status command returns the local NetBIOS name

table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type

nbtstat -s at the
command prompt, and then press ENTER. This command 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
-------------------------------------------------------

-----------
DAVEMAC1 00 Connected Out CNSSUP120 6MB

5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB

116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB

19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB

19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool,

type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command,

ping the desired
host using its host name.

If the ping command fails with an Unable to resolve

target system name
message, verify that the host name is correct and that

the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the

IP address of the
computer. If pinging the IP address is successful, but

pinging the computer
name is not, you might have a name resolution problem. In

this case, ensure
that the computer name you are specifying can be resolved

through the local
Hosts file, by using Domain Name System (DNS) queries, or

through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes

of data:
====

To ping the destination ###.###.###.### and resolve

###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on

the destination IP
address. If this is successful, ping displays the

corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I

Cannot "Ping" It by Name
If you can contact a resource by using its IP address but

a PING message to
its host name does not work, the problem may be caused by

a name resolution
failure, instead of by network connectivity. Make sure

that the computer is
configured with the correct DNS or WINS entries, and that

the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and

then press ENTER.

At the command prompt, type net view \\ComputerName, and

then press ENTER,
where ComputerName is the name of the computer that you

want to connect to.

A list of the file and print shares on that computer is

generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the

specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and

you receive a
"System error has occurred" error message, follow these

steps:
Verify that you typed the correct name of the remote

computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer

Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways

(routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work,

type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command

works, but the NET VIEW
\\ComputerName command does not work, the computer name

may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool,

type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and

pecked:
No, it happens with all addresses except for servers

which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

.

  #60  
Old April 18th 04, 01:39 PM
Lois
external usenet poster
 
Posts: n/a
Default Tracert in XP

Thanks Wesley
Nbtstat -a gives me exactly what I need.
-----Original Message-----
Could very well be.

HOW TO: Diagnose and Test TCP/IP or NetBIOS Network

Connections in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-

us;323388

To Display Connection Information by Using the

Nbtstat.exe Tool
[[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 lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS

name resolution
problems. You can use the NBTSTAT command to remove or

correct preloaded
entries. To use the NBTSTAT command:
To list the NetBIOS table of the local computer, type

nbtstat -n at the
command prompt, and then press ENTER. This command

returns the NetBIOS local
name table. It indicates whether each name is a unique

name or a group name
and whether the name is registered or unregistered on the

network.

To list the contents of the NetBIOS name cache, type

nbtstat -c at the
command prompt, and then press ENTER. This command shows

the NetBIOS name
cache, which contains name-to-address mappings for other

computers.

To clear the contents of the name cache and reload it

from the LMHOSTS file,
type nbtstat -R at the command prompt, and then press

ENTER.

NOTE: Make sure that you use an uppercase "R".

To display the name table of a remote computer, type

nbtstat -a
RemoteComputerName at the command prompt, and then press

ENTER, where
RemoteComputerName is the NetBIOS computer name of the

remote computer. The
adapter status command returns the local NetBIOS name

table for that
computer and the MAC address of the network adapter.

To display a list of client and server connections, type

nbtstat -s at the
command prompt, and then press ENTER. This command 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
-------------------------------------------------------

-----------
DAVEMAC1 00 Connected Out CNSSUP120 6MB

5MB
DAVEMAC1 00 Connected Out CNSPRINT20 108KB

116KB
DAVEMAC1 00 Connected Out CNSSRC120 299KB

19KB
DAVEMAC1 00 Connected Out STH2NT20 324KB

19KB
DAVEMAC1 03 Listening

NOTE: To see additional options of the Nbtstat.exe tool,

type nbtstat /? at
the command prompt.]]
===============

[[To test host name resolution by using the ping command,

ping the desired
host using its host name.

If the ping command fails with an Unable to resolve

target system name
message, verify that the host name is correct and that

the host name can be
resolved by your DNS server.]]

[[You can use ping to test both the computer name and the

IP address of the
computer. If pinging the IP address is successful, but

pinging the computer
name is not, you might have a name resolution problem. In

this case, ensure
that the computer name you are specifying can be resolved

through the local
Hosts file, by using Domain Name System (DNS) queries, or

through NetBIOS
name resolution techniques.]]

Start | Run | Type: cmd | OK |
Type: ping example.microsoft.com | ENTER

Does it return???

Pinging microsoftoffice.com [65.54.206.30] with 32 bytes

of data:
====

To ping the destination ###.###.###.### and resolve

###.###.###.### to its
host name.
Where ###.###.###.### is the IP address

The -a switch...
[[Specifies that reverse name resolution is performed on

the destination IP
address. If this is successful, ping displays the

corresponding host name.]]

Try pinging the address you keep refering to:

ping -a ###.###.###.###
===

[[I Can Ping a Resource by Its IP Address, but I

Cannot "Ping" It by Name
If you can contact a resource by using its IP address but

a PING message to
its host name does not work, the problem may be caused by

a name resolution
failure, instead of by network connectivity. Make sure

that the computer is
configured with the correct DNS or WINS entries, and that

the DNS or WINS
servers are available.]]
===========

To Test Connections by Using the NET VIEW Command
[[Click Start, click Run, type cmd in the Open box, and

then press ENTER.

At the command prompt, type net view \\ComputerName, and

then press ENTER,
where ComputerName is the name of the computer that you

want to connect to.

A list of the file and print shares on that computer is

generated by
establishing a temporary NetBIOS connection.

If there are no file or print shares available on the

specified computer,
you receive a "There are no entries in the list" message.

If the NET VIEW \\ComputerName command does not work and

you receive a
"System error has occurred" error message, follow these

steps:
Verify that you typed the correct name of the remote

computer.
Verify that the computer is operational.
Verify that the computer is running the File and Printer

Sharing for
Microsoft Networks service.

Use the PING command to verify that all the gateways

(routers) between the
local computer and the remote host are operational.

If the NET VIEW \\ComputerName command does not work,

type net view
\\IPAddressOfRemoteComputer, and then press ENTER.

If the NET VIEW \\IPAddressOfRemoteComputer command

works, but the NET VIEW
\\ComputerName command does not work, the computer name

may be resolving to
the wrong address.
NOTE: To see additional options of the Net View tool,

type net view /? at
the command prompt.
===============
--
Hope this helps. Let us know.
Wes

In ,
Lois hunted and

pecked:
No, it happens with all addresses except for servers

which
are listed in the DNS. So apparently it is somehow DNS
related?
-----Original Message-----
Lois;

Is 192.168.0.118 the only address this happens with???


--
Hope this helps. Let us know.
Wes


SNIP

.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 12:43 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.