Chuck:
Big apology for not following directions fully. I have
included the IPCONFIG /ALL output from all three machines
on the network, but BROWSTAT did not run on the Win98
machines (said it was linked to missing NETAPI32.DLL), so
I've only included the BROWSTAT from the WinXP machine.
I was also remiss is not mentioning that WinXP machine
has had VPN software installed on it, although I believe
I was able to network resources by name since VPN was
installed; it's only recently that I cannot do it.
Again, thanks for all your assistance.
Don't sweat it, Ron. Sometimes it just takes a few tries.
Anyway, one answer was there.
Windows IP Configuration
Host Name . . . . . . . . . . . . : HP_NOTEBOOK
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
Node type Peer-Peer is a problem. That means HP_NOTEBOOK needs a WINS server to
resolve names. No WINS server, no name resolution.
Here's the Microsoft article discussing node types:
<
http://support.microsoft.com/?id=314053>
To correct this, you'll need to run the Registry Editor on HP_NOTEBOOK.
You need to find this key:
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
and delete these two values (which ever is there):
NodeType
DhcpNodeType
After you delete the two values, reboot the computer. After the reboot, rerun
IPConfig and post the results.
The Registry Editor is a scary tool, but it's pretty simple once you get used to
it. Here are a couple articles that might help:
<
http://www.microsoft.com/windowsxp/...home/using/productdoc/en/tools_regeditors.asp>
<
http://www.annoyances.org/exec/show/registry>
Just remember to backup the key (create a registry patch) for:
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
before deleting the values.
From the Annoyances article:
You can create a Registry patch by opening the Registry Editor, selecting a
branch, and choosing Export from the File menu. Then, specify a filename, and
press OK. You can then view the Registry patch file by opening it in Notepad
(right-click on it and select Edit). Again, just double-click on a Registry
patch file (or use Import in the Registry Editor's File menu) to apply it to the
registry.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.