My Network Places cannot see certain pc's

[Haggis]

Hello all,

I have 30+ pc's on a network , 2 workgroups ...htey were all win9x until I
dropped a winxp pro sp1 box in the mix...

I cannot see 3 or 4 of the pc's (running 9x) from the new XP box. I can ping
them buy name or IP no problem (command prompt), but they do not show in My
Network Places.(even when searching specifically for them)

all machines use netbeui for file sharing (tcp/ip installed for internet
access but not bound for file sharing)

a DHCP router is in use ..all ip's are 192.168.1.xxx

pc's that cannot be seen are win95 or win98se (updates installed and
verified)

I have looked at many articles describing this problem and none seem to have
fixed this little problem.

Thought's anyone?

thank you
Dave

 

[Nico Tomacelli [MSFT]]

Hi Haggis?

I see two issues here:

1) Net Crawler, the program that automatically detects the shares on the
other computers in the network will stop after the 32nd machine.
So it can only populate shares from the first 32 machines it finds.

2)
You should still be able to see the computers though. Are you clicking on
"View workgroup computers"?
How are you searching for them within My Network Places?

Thanks,
Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
=====================================================

 

[Haggis]

Hi Nico...I thought Haggis was a neat name :>

Hi Haggis?

I see two issues here:

1) Net Crawler, the program that automatically detects the shares on the
other computers in the network will stop after the 32nd machine.
So it can only populate shares from the first 32 machines it finds.

ans: I have exactly 32 machines on the network (all win9X except for the new
one)...do you mean 32 shares as in 32 objects shared?(HD,CDROM,etc)
but i still should be able to see pc's if searched on...

2)
You should still be able to see the computers though. Are you clicking on
"View workgroup computers"?
How are you searching for them within My Network Places?

cannot see them at all .... can ping by name and IP at command prompt , do
search from start menu (name and IP) no go ...same if in network places.

Thanks
Dave

 

[Nico Tomacelli [MSFT]]

Sorry, I didnt mean a question mark

Actually, I didn't mean shares, I meant machines. It will only pick up
shares from the first 32 machines. Since you have exactly 32 machines, that
should be an issue.

What happens if you try and connect to these machines that it cannot see?
Is it a certain few that it cant see or is it random?

Thx,
Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
=====================================================

 

[Haggis]

Sorry, I didnt mean a question mark

I've had a few remarks on the name is all :>

Actually, I didn't mean shares, I meant machines. It will only pick up
shares from the first 32 machines. Since you have exactly 32 machines, that
should be an issue.

is that supposed to read "shouldn't be an issue"?

What happens if you try and connect to these machines that it cannot see?
Is it a certain few that it cant see or is it random?

3 pc's win95 (workgroupA) and 2 machines win98se (workgroupB)...
NET USE will not work (which is why I can't understand why PING and TRACERT
would work)

all protocols set the same (netbeui for file sharing and tcp/ip(unbound for
file sharing)) I have no other problems connecting to other pc's in either
workgroup.

I am about to go remave all networking items from one of them and let it
reinstall...(sharp stick...poke poke) :>


Thks!
Dave(Haggis)

 

[Nico Tomacelli [MSFT]]

Hi Haggis, I've had people butcher my name as well

yes, that was suppose to be shouldn't.

Steve Winogard, a MS MVP has some good tips for getting Networking to work.
You may want to try the following listed below..I believe you have already
tried a couple of these.

Let me know if any of this helps.

1. Are the machines having the problem running any firewall type program
like Zone Alarm?

2. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm

4. Run "ipconfig /all" on XP and look at the "Node Type" at the
beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053


Thanks.
Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
=====================================================

 

[Haggis]

Thanks Nico,

I've got Steve's site (and a few others)
and I have tried all of what you have listed below ...

we use a hardware firewall to outside....
I am only running tcp/ip right now on all machines BUT still cannot connect
to some (can still ping them ..name and IP) but no network place ...

I am running symantec corp. managed antivirus on all machines(i don't think
that's it)

I'm going to have to think about it over the weekend ...don't know what to
try next??!?

Thanks

Haggis

 

[Guest]

What if the node type in ipconfig is "unknown"?

----- Nico Tomacelli [MSFT] wrote: -----

Hi Haggis, I've had people butcher my name as well

yes, that was suppose to be shouldn't.

Steve Winogard, a MS MVP has some good tips for getting Networking to work.
You may want to try the following listed below..I believe you have already
tried a couple of these.

Let me know if any of this helps.

1. Are the machines having the problem running any firewall type program
like Zone Alarm?

2. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm

4. Run "ipconfig /all" on XP and look at the "Node Type" at the
beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053


Thanks.
Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
=====================================================

 

[Haggis]

"unknown" is ok

What if the node type in ipconfig is "unknown"?

----- Nico Tomacelli [MSFT] wrote: -----

Hi Haggis, I've had people butcher my name as well

yes, that was suppose to be shouldn't.

Steve Winogard, a MS MVP has some good tips for getting Networking to work.
You may want to try the following listed below..I believe you have already
tried a couple of these.

Let me know if any of this helps.

1. Are the machines having the problem running any firewall type program
like Zone Alarm?

2. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm

4. Run "ipconfig /all" on XP and look at the "Node Type" at the
beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053


Thanks.
Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
=====================================================

"Nico Tomacelli [MSFT]" <[email protected]> wrote in

message

Sorry, I didnt mean a question mark
I've had a few remarks on the name is all :>>>> Actually, I didn't mean shares, I meant machines. It will only pick up
shares from the first 32 machines. Since you have exactly 32

machines,
that

should be an issue.
is that supposed to read "shouldn't be an issue"?
What happens if you try and connect to these machines that it

cannot

see?
NET USE will not work (which is why I can't understand why PING

and

TRACERT
would work)

tcp/ip(unbound

for
file sharing)) I have no other problems connecting to other pc's in either
workgroup. let it
reinstall...(sharp stick...poke poke) :>>>> Thks!
Dave(Haggis) no
rights.

shares

on

except for
the prompt

,

XP box.
I

not
show

installed

and

none

seem