Home Network setup sharing problems ...

Status
Not open for further replies.

Emkorial

Ars Legatus Legionis
33,592
Subscriptor
Ok, here's the situation. I got 2 PC's. Both have NIC's. I have an 8 port hub and an ecternal cable modem. Both PC's have different IP's so they can both be on the Internet at the same time. I've setup File and print sharing on both PC's, yet when I click on network neighborhood, the PC's only see themselves, not each other. Both PC's are in the same workgroup. Any idea's, oh ars gurus?
 

Grifter

Wise, Aged Ars Veteran
178
Make sure you give them IP addresses, I'm not quite sure if it'll conflict with the internet connection, I have two NIC's in one computer and use SyGate to share the connection, maybe someone else could better tell you about that. Another thing, I once read somewhere that each computer must be sharing at least one folder in order to see it. Don't know for sure that it's true but it seemed to fix my problem once.
 
Ideas:

- See if they can ping each others' IP addresses
- See if they can be found with the Find Computer util
- Netmasks have to be the same, must have TCP/IP installed
- Yes, as Grifter said they must be sharing a folder in order to show up on the browse list. A Comp won't show up AT ALL if it's not sharing a folder or printer (this means in it's own Net Neighborhood folder)
- A misconfigured NIC can often cause similar problems to yours ... tough to find which one with only two PC's though ...

Hope this helps!

 

Emkorial

Ars Legatus Legionis
33,592
Subscriptor
Well, both PC's are in the same workgroup, aptly named "workgroup". However, being on an @home cable modem, The IP and Subnet are all server assigned. I tried assigning it manually with the numbers they gave me, and wa-laa, no internet connection. It is required that both have defined subnets, or since they are both server assigned from the server will they always be the same? I'll have to do a winipcfg when I'm home to check that.
 

flipside

Ars Tribunus Militum
1,725
Mmmm, just a guess...and you probably know this, but, ah...
...if pinging actually works and you only have tcp/ip protocol installed you need to enter the id/computer name in the lmhost file for them to show up in the nw neighbourhood. That, or use the ip to map network drives.

search for "lmhosts.sam" (win2k, w98 prolly just "lmhost(s)" ), open it in the editor and add e.g "10.0.0.1 yourcomputername" at the bottom.


[This message was edited by flipside on June 22, 2000 at 13:16.]
 
Be aware that by connecting your LAN directly to the Internet, you risk sharing your files and printers with the entire planet. To avoid this, install NetBeui on both machines and bind the Windows network services only to that, not to TCP/IP. See http://www.timhiggins.com/ppd/securnet.htm for details.

You may also want to pick a more unique workgroup name than "workgroup". I'm guessing there's a lot of directly connected machines out there in the "workgroup" workgroup, and it seems best to steer clear of them.

The most secure approach is probably to get a NAT-capable hardware router such as the Netgear RT311 and use that to isolate your home LAN from the Net at large.
 

Emkorial

Ars Legatus Legionis
33,592
Subscriptor
Ok, I went back and created some really strange workgroup name, put both PC's on the workgroup. I installed NetBUI on both machines, binded it to File and Printer sharing, and unbound TCP/IP, and wa-laa! it works.

Of course, its pretty much an exercise in futility, cause my girlfriend doesn't play computer games anyway, but it was fun :)
 

*Iridium*

Ars Praefectus
3,499
Subscriptor
You might be surprised at how useful it is. I did it "just for grins" but I use it all the time. I've turned my old P133 into a game machine and can play most games including Q3test over the connection. It's also handy when you get a new system and can just pick files and proggies off any machine without using the sneaker net. Next I'm getting something like PC Anywhere so I can dial up and talk to my main machine when on the road. Fun!
 
Status
Not open for further replies.