Once again - W2000 comp unable to see others in network ARRRRGG

[Alex DeLarge]

4 computers on the network connecting by cat cable through a Linksys
cable modem router.
All computers are in same workgroup. All names are unique. All are
assigned consecutive IP's by router
192.168.1.100 through 192.168.1.103 All have subnet of 255.255.255.0
NetBIOS through TPC/IP enabled on all.

Here's the deal O'Neal

None have firewall software running

Computer 100 is Thinkpad R series running XP pro - Fire wall is off

sees internet, 101, 102, 103

Computer 101 is home built running W2000 pro - 3com nic

sees internet, 100, 102 but does not see 103

Computer 102 is home built running W2000 pro - 3com nic

sees internet, 100, 101 but does not see 103

Computer 103 is Thinkpad 600E running W2000 pro - Netgear or Linksys
pcmcia ethernet card

sees internet, 100

Irregardless as to which card is used, this computer does not
see the 2 other computers running W2000 - comps 101 and 102 - the
comps that can't see this computer.

Pinging the IP addresses nets the return of "time out"

Full permissions are granted.
Same users and passwords on each computer

I give up.

 

[Shilpa Sinha [MSFT]]

Hi

Maybe this will help:

Windows 2000 Client with NetBIOS Scope Cannot Communicate with Other
Windows 2000 Clients

SYMPTOMS
==============
Windows 2000-based clients that are using a NetBIOS scope may be unable to
communicate with other Windows 2000-based clients, even though they are in
the same scope. Microsoft Windows NT 4.0-based clients can communicate with
the Windows 2000-based host, even though they cannot see each other.

CAUSE
==========
The clients are unable to connect to each other with a Server Message Block
(SMB) session. A TCP session is established successfully and the calling
computer sends a negotiate packet to the target computer, but the target
computer never responds. The calling computer then cleans up the session
after the time-out period has been reached.

RESOLUTION
===============
A supported fix is now available from Microsoft, but it is only intended to
correct the problem that is described in this article. Apply it only to
computers that are experiencing this specific problem. This fix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next Windows 2000
service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the fix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit
the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support
calls may be canceled if a Microsoft Support Professional determines that a
specific update will resolve your problem. The typical support costs will
apply to additional support questions and issues that do not qualify for
the specific update in question.

The English version of this fix should have the following file attributes
or later:

Date Time Size File name
--------------------------------------------------------
03/17/2000 01:08p 190,896 Q257306_w2k_sp1_x86_en.exe


STATUS
==============
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article.

MORE INFORMATION
========================
NOTE: The use of NetBIOS scopes as described in this article is included
only as a convenience for limited situations in which they absolutely must
be used, and no other alternatives exist (such as VLANs, IPSec, more
restrictive use of NTFS and share security, and so on). The use of NetBIOS
scopes is discouraged, and there are no guarantees that NetBIOS scopes will
be supported in future releases of Microsoft products.
The information in this article applies to:

o Microsoft Windows 2000 Server
o Microsoft Windows 2000 Professional


Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[serverguy]

One thing you could try is a cross-over cable run between 103 and 101 or 102
(give them static ips). If it works, this will tell you many things: it
could be router/firewall related, it is probably not a problem with the nics
communicating with each other, there is likely nothing wrong with o/s
settings.

If they still cannot see each other with the cross-over cable, then the
router settings are probably not the problem, and you need to look at nic
drivers and settings, and other bare-basic network settings on that 103
machine.

Check the event logs on all the machines.

 

[Alex DeLarge]

Thanks for the tip. I'll give it a go and let you know what the
results are.

 

[Alex DeLarge]

After doing a check with the crossover cable and being able to see the
network I delved into the Router/firewall troubleshooting route.

On a whim I thought that since I had to assign an IP for the crossover
connection maybe if I assign my own static IP instead of allowing the
DHCP of the router I'd get different results. I assigned a static IP,
gateway and DNS and BINGO!! Everyone is visable and the file sharing
and printer sharing and mama and everyone is happy

Thanks for the suggestions.

 

[Alex DeLarge]

After the tip to test with a crossover cable (which proved
successful) the machines could see each other - I decided to delve
into the router/firewall debacle.

I thought for a lark that since I had to assign a static IP to do the
crossover test - why not try assigning a static IP to the problematic
machine instead DHCP.
So I assigned a static IP and DNS and presto - all are visible to each
other.

File sharing and printer sharing and mama and everyone is happy and I
thank you for your advise. Hopefully this little lesson will benefit
someone else with their networking problems.

 

[serverguy]

Good new! Thanks for sharing your solution.

After the tip to test with a crossover cable (which proved
successful) the machines could see each other - I decided to delve
into the router/firewall debacle.

I thought for a lark that since I had to assign a static IP to do the
crossover test - why not try assigning a static IP to the problematic
machine instead DHCP.
So I assigned a static IP and DNS and presto - all are visible to each
other.

File sharing and printer sharing and mama and everyone is happy and I
thank you for your advise. Hopefully this little lesson will benefit
someone else with their networking problems.