Dude, where's my LAN?!

  • Thread starter Thread starter Hank Zoeller
  • Start date Start date
H

Hank Zoeller

Hello,

I am running a machine with WinXP-Pro SP2 (firewall disabled), another
machine with Win2K-Pro SP3 and two UNIX machines (Solaris). All
machines are connected to a hub which is, in turn, connected to a
firewall router - except the Win2K machine which uses a wireless
connection to the firewall/router. The Windows machines are all members
of a workgroup.

The Windows machines use DHCP and have valid IP addresses assigned. The
UNIX machines all have fixed IP addresses. All machines IP addresses
are in the 192.168.0.xxx range (subnet 255.255.255.0). There is also a
printer sitting on 192.168.0.100. All the machines can print to the
printer, see the internet, dns, browse the web, send and receive email,
etc. etc.

The problem is seeing the internal LAN..

The WinXP machine and the Win2K machine can ping each other but can NOT
see shares or map drives or anything else. The Windows machines do not
seem to see the LAN other than themselves and printing on the LAN
printer (via TCP/IP).

The UNIX machines can see the workgroup but can only see the WinXP
shares -- NOT the Win2K shares.

On both Windows machines I'm running Client for MS Networks, File and
Printer Sharing for MS Networks and Internet Prototcol (TCP/IP). (And,
all are enabled.) The Win2K machine also has NetBEUI running.

Each Windows machine has shares but can only see it's own shares.

So, where's my LAN? What am I doing wrong?

Thank you,
-Hank
 
Hank said:
Hello, ....snippage of all...
So, where's my LAN? What am I doing wrong?
Click to expand...

OK, problem solved. I realized that I needed to have DHCP help with
NetBIOS name resolution so on each Windows box I went to Advanced TCP/IP
settings, WINS tab and set the NetBIOS setting to be "Use NetBIOS
setting from the DHCP server".

That got me to the point where I could at least see the other machines
on the LAN although I still couldn't open the shares.

Then, I stumbled upon this:
http://forums.devshed.com/archive/t-150645

The registry hack therein solved my problem.

So, now, I can still use DHCP, don't need no steenkin' LMHOST solution
and I can browse my network like I should have been able to out of the box..

Thank you all for reading along. <yawn...>
 
Hank said:
Hank Zoeller wrote: ....snippage...
Then, I stumbled upon this:
http://forums.devshed.com/archive/t-150645
Click to expand...

OK, for the archives, here's what MSDN has to say about the registry
hack from above (see article Q160177):

// start MSDN quote
NodeType
Key: Netbt\Parameters
Value Type: REG_DWORD - Number
Valid Range: 1,2,4,8 (B-node, P-node, M-node, H-node)
Default: 1 or 8 based on the WINS server configuration
Description: This parameter determines what methods NetBT will use to
register and resolve names. A B-node system uses broadcasts. A P-node
system uses only point- to-point name queries to a name server (WINS).
An M-node system broadcasts first, then queries the name server. An
H-node system queries the name server first, then broadcasts. Resolution
via LMHOSTS and/or DNS, if enabled, will follow the these methods. If
this key is present it will override the DhcpNodeType key. If neither
key is present, the system defaults to Bnode if there are no WINS
servers configured for the network. The system defaults to Hnode if
there is at least one WINS server configured.
// end MSDN quote

That is all. Carry on...
 
Back
Top