Can Ping but not see the other PC 2

[IFRs]

I have a small home LAN. CAT5 Wired.
2 Dell laptops. One brand new, one 2 years old.
New one has XP Pro, old one has Win2000
Broadband router shares cable modem with them.
Both have C drive shared.
Both have unique comptuer names.
Both on workgroup "HOME", uppercased.

I can:
surf the web on both
ping both from each other

I can't:
see the other computer in Network Neighborhood. All I see is the PC I'm on when I browse the network.

How can I share resources? I must be missing something simple, but I can't think of what it is!!!

 

[Gersen]

thanks for the info, bcastner! Would a request on the same subnet ever be processed by the router, or would it broadcast for name resolution?

As for IFRs workstations, I have a question. I understand your router is at 192.168.0.1, and your workstations are at addresses 192.168.0.2 and at 192.168.0.3. But what is at the address they are using for DNS resolution, 192.168.100.1?

 

[IFRs]

Gersen -
192.168.100.1 is the IP of the cable modem

 

[bcastner]

IFRS,

That does not sound right to me. The modem should be accessible through the router Gateway. The DNS entries being pulled should be those of your ISP's DNS servers.

In any case since the cable modem is showing a private, not public IP address, it appears as if they modem has some inbuilt router capability.

Set all the client addresses manually, the only change from the DHCP addresses you obtained above is that you need to be outside the DHCP scope of your router, or just disable DHCP in the router setup.

You should point the DNS address manually to 192.168.0.1, and let the router handle DNS forwarding.

 

[Gersen]

So your setup looks something like this:

==cable==>[Cable Modem]=====>[Router/Switch]====>Laptop1
\\===>Laptop2

with the Laptops pointing to the Cable Modem for name resolution, and the Cable Modem pointing to the Internet for name resolution, and we're assuming the Cable Modem points to your ISP's DNS servers...

It seems like the inside interface of your Cable Modem is already on a private subnet, which is not what I usually encounter with cable Internet.

Method 1
Personally in this setup, I would not connect your Cable Modem to the WAN port of your Router at all! I would plug it into the switch, and as bcastner suggests I would disable DHCP on the router, letting the Cable Modem handle the DHCP on the internal network.

Method 2
I know some cable companies will only allow one machine to authenticate, in which case you have to go through the router, but in that setup I would set up my Cable Modem and Router (if possible) to communicate on public Internet addresses and then have my Router convert to a private (192.168.0.X) address scheme.

I have 2 clients with cable modems, and I have one of them set up each of the 2 ways I just described, each based on how their service works, and what options are available to them. Sorry I can't nail it down more without getting my hands on your setup. You should probably try bcastner's above suggestion first.

 

[IFRs]

Well, I finally got around to visitng my friend again and having another go at his LAN problems. What fun !!!

We added an old Win98 box to the mix. It has a login name and password.

We changed the router for a Linksys which I am much more familiar with, figuring that if we got it all working with the Linksys we might be able to switch over to the Greyfox.

We added a login name and password to the new WinXP laptop.

We now have:
(1) WinXP laptop on workgroup HOME
(2) Win98 box on workgroup HOME
(3) Win2000 laptop on domain matrixservice.com

All 3 have login names and passwords.

All 3 have

http://www access.

The WinXP laptop and the Win2000 laptop can access the Win98 box by browsing to it's IP address but not \\name.

The Win98 box can not get to any of the other shares. Neither shows up in My Network Places and neither can be browsed to using \\name or \\IP address. Considering the needed funtionality of the LAN, I'm willing to give this one up.

None of the three laptops show up in the My Network Places (or it's equivalent) of either of the two other machines. Only the local machine shows up. I would expect this of the Win2000 laptop because it is not a member of the HOME workgroup. I'm willing to accept it on the Win98 box because, well - just because. I'm surprised that the WinXP laptop does not see the Win98 box in it's network neighborhood or the HOME workgroup.

I can't seem to get the WinXP laptop to login to the Win2000 laptop using DOMAIN\User or computername.DOMAIN\User in the Name field and that User's password. Is it because I'm trying to log into the Win2000 laptop with the same name/password as the person who is currently logged into it?

From the Win2000 laptop I can ping the WinXP laptop but not browse to it using \\IP address or \\name.

 

[bcastner]

You do not logon remotely to the laptop that is set as a domain member. It is not a domain server, just a workstation that is a domain member.

It is helpful that the Winxp laptop now has a username and password at logon. But it does sound as if you have not taken the step on all three machines to enable Netbios over TCP/IP. This is not done by the router/DHCP server, but is a manual entry on your part on all three machines.

In XP, you look at the Properties Sheet for the local area connection, TCP/IP Properties, Advanced, WINs tab, check to enable Netbios over TCP/Ip and disable LHMHOSTS.

There is a similar setting under the lan adapter/TCP/IP properties sheet under Windows 98.

I think a more comprehensive checklist might light a bulb for you somewhere, or perhaps a whole chandelier:

Simple File Sharing -- Enabled

http://www.practicallynetworked.com/sharing/xp/filesharing.htm

Simple File Sharing -- Disabled

http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm

 

[IFRs]

bcastner -

When I try to access the Win2000 laptop from the WinXP laptop by putting \\ip address in a folder view, up pops up a login screen. It seemed logical to me that it ask for authentication on the Win2000 laptop since the Win2000 laptop is not part of the HOME workgroup. Not??

I'll check NetBIOS but I think they are all enabled over TCP/IP.

I think LMHOSTS are disabled on all but again, I will check.

 

[bcastner]

Yes, in that context it is logical. But it would not do the prompting unless the following from early above was not done:

". All username/passwords of computer A made users with passwords on computer B, and vice-versa;"

In addition, you want to make certain that on the shares you make on each computer that both the Share Permissions, and the NTFS permissions (two steps) are made to permit access from the remote workstation.

 

[Gersen]

We've obviously reached a point where you're problem has been narrowed down to name resolution on the local network. Even a permissions problem would not keep a user from seeing the other machines while browsing the network, however. It would simply demand authentication when trying to connect to a shared resource.

bcastner, wouldn't the line "Node Type . . . . : Hybrid" in each of the ipconfig dumps above indicate that the laptops are already set up with NetBIOS and able to resolve names by broadcast?

IFRs, you should still be able to browse to a machine on a different workgroup, assuming Windows networking is all set up correctly. When you open "Entire Network", it would show first the various workgroups you can see, then the individual machines would be visible when you open each workgroup.

As a diagnostic test, you can set your node type
manually in the registry on the machines, assuming you're comortable with editing the registry. I quote from a post:

"You need to edit this key in your registry. Normal disclaimers apply if you don't know what you're doing.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters

DhcpNodeType should be 8, not 2, to enable broadcast lookups. You can release and then renew ipconfig to pick up the change." (end quote)



There are only 10 kinds of people; those who understand binary and those who don't...

 

[Stringbender]

I kind of briefly skimmed over all these posts related to IFRs's home networking problem. This may have been an obviously tried resolution, but I had no problems "home networking" a Win XP and a Win 98 machine. I took the very easy way out and used the "Create Home Network" wizard available in Win XP. It runs through a few general questions and creates a "floppy" that you simply insert into any other computers that you wish to become part of the network. I hope this helps in some way.