Unable to connect using computer name

I have a peer to peer home network. 2 XP computers & a Windows 2000 one
connect to each other with no trouble.

The 4th is a Windows 98 desktop which the other can connect to OK. On this
computer however:
- If I try to connect using map drive and specifying the name of another
computer it will never connect.
- If I try map drive & use the IP address of another computer it connects
with no problem
- If I use "find computer" and use a computer name it will not find it
- If I use "find computer" and an IP address it always finds it
- If I find it via the IP but without connecting to it or mapping anything I
go to map drive and try and map via the computer name it now connects no
trouble.

What can cause this annoying behaviour?

I want to run a batch file with the command "net use \\computername\path
password" to set up the mapped drive automatically but it will not connect
and I can't use the IP because it is allocated dynamically and can change.
I can't use reconnect at logon because my wireless card does not get
registered until after the reconnect tries & fails.





Lorne

In article <(E-Mail Removed)>, "Lorne"
<(E-Mail Removed)> wrote:
>I have a peer to peer home network. 2 XP computers & a Windows 2000 one
>connect to each other with no trouble.
>
>The 4th is a Windows 98 desktop which the other can connect to OK. On this
>computer however:
>- If I try to connect using map drive and specifying the name of another
>computer it will never connect.
>- If I try map drive & use the IP address of another computer it connects
>with no problem
>- If I use "find computer" and use a computer name it will not find it
>- If I use "find computer" and an IP address it always finds it
>- If I find it via the IP but without connecting to it or mapping anything I
>go to map drive and try and map via the computer name it now connects no
>trouble.
>
>What can cause this annoying behaviour?
>
>I want to run a batch file with the command "net use \\computername\path
>password" to set up the mapped drive automatically but it will not connect
>and I can't use the IP because it is allocated dynamically and can change.
>I can't use reconnect at logon because my wireless card does not get
>registered until after the reconnect tries & fails.

Make sure that NetBIOS Over TCP/IP is enabled on all computers, as
shown here:

http://www.practicallynetworked.com/...hoot/netbt.htm
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <(E-Mail Removed)>, "Lorne"
> <(E-Mail Removed)> wrote:
>>I have a peer to peer home network. 2 XP computers & a Windows 2000 one
>>connect to each other with no trouble.
>>
>>The 4th is a Windows 98 desktop which the other can connect to OK. On
>>this
>>computer however:
>>- If I try to connect using map drive and specifying the name of another
>>computer it will never connect.
>>- If I try map drive & use the IP address of another computer it connects
>>with no problem
>>- If I use "find computer" and use a computer name it will not find it
>>- If I use "find computer" and an IP address it always finds it
>>- If I find it via the IP but without connecting to it or mapping anything
>>I
>>go to map drive and try and map via the computer name it now connects no
>>trouble.
>>
>>What can cause this annoying behaviour?
>>
>>I want to run a batch file with the command "net use \\computername\path
>>password" to set up the mapped drive automatically but it will not connect
>>and I can't use the IP because it is allocated dynamically and can change.
>>I can't use reconnect at logon because my wireless card does not get
>>registered until after the reconnect tries & fails.
>
> Make sure that NetBIOS Over TCP/IP is enabled on all computers, as
> shown here:
>
> http://www.practicallynetworked.com/...hoot/netbt.htm

NetBIOS is enabled on all machines. I noticed the XP machine has LMHosts
Lookup enabled - I have no idea what that is but I assume it is OK.

Any other ideas?

In case it helps I can map to the 98 machine from the XP one using the
computer name but the 98 machine does not show up under my workgroup name
using explorer nor does the XP computer show up using explorer on the 98
machine.

I have also tried shutting down ZoneAlarm to no effect (it has the
192.168.0.0..255 range set as trusted anyway).

"Lorne" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> In article <(E-Mail Removed)>, "Lorne"
>> <(E-Mail Removed)> wrote:
>>>I have a peer to peer home network. 2 XP computers & a Windows 2000 one
>>>connect to each other with no trouble.
>>>
>>>The 4th is a Windows 98 desktop which the other can connect to OK. On
>>>this
>>>computer however:
>>>- If I try to connect using map drive and specifying the name of another
>>>computer it will never connect.
>>>- If I try map drive & use the IP address of another computer it connects
>>>with no problem
>>>- If I use "find computer" and use a computer name it will not find it
>>>- If I use "find computer" and an IP address it always finds it
>>>- If I find it via the IP but without connecting to it or mapping
>>>anything I
>>>go to map drive and try and map via the computer name it now connects no
>>>trouble.
>>>
>>>What can cause this annoying behaviour?
>>>
>>>I want to run a batch file with the command "net use \\computername\path
>>>password" to set up the mapped drive automatically but it will not
>>>connect
>>>and I can't use the IP because it is allocated dynamically and can
>>>change.
>>>I can't use reconnect at logon because my wireless card does not get
>>>registered until after the reconnect tries & fails.
>>
>> Make sure that NetBIOS Over TCP/IP is enabled on all computers, as
>> shown here:
>>
>> http://www.practicallynetworked.com/...hoot/netbt.htm
>
> NetBIOS is enabled on all machines. I noticed the XP machine has LMHosts
> Lookup enabled - I have no idea what that is but I assume it is OK.
>
> Any other ideas?
>
> In case it helps I can map to the 98 machine from the XP one using the
> computer name but the 98 machine does not show up under my workgroup name
> using explorer nor does the XP computer show up using explorer on the 98
> machine.
>
> I have also tried shutting down ZoneAlarm to no effect (it has the
> 192.168.0.0..255 range set as trusted anyway).
>

un-install ZoneAlarm until you have your network connecting properly (not
just disable)

the hosts file is explained here

http://www.mvps.org/winhelp2002/hosts.htm