Home LAN no good either.

[vyper2000]

Hello there,

From one techie to another, I need some advice. My home LAN was working, even after the external cable modem was attached to it by Charter Pipeline. Well, I reformatted my machine since then, and I can't see the other 2 machines on my home LAN. The other two can still each other. I've ensured that I am using the same "workgroup" name, and that my computer name is not the same as any of the others.
The TCP/IP for Ethernet is set to "obtain IP address automatically." It has to be since that's the connection routine for Charter Pipeline. I also ensured that I have the IPX/Spx for Ethernet installed as well for my D-Link 10/100 card. I have even shut off the cable modem, powered down all machines, powered them up, followed by the cable modem, and still can't see the other machines on my home LAN.

Another insteresting point here is that when I click my Network Neighborhood, I can see the other machines, well some of them, that are from other Charter Pipeline users. I can see my workgroup name listed. I click it, and only my machine shows up. Now, on either of the other two computers, I do the same thing, and I can see both of them listed for the same workgroup name. What is the deal here? I have no IP spooking utilities installed to keep my machine in stealth mode, as Zone Alarm does. I have file and print sharing turned on. I also boot up with Client for MS Networking.

Any ideas on what I am missing or should do at this point?

Thanks for your time,

Christopher (cable_cruncher@hotmail.com)

------------------

[glc1]

Ah, you lost me. http://www.speedguide.net/ubb/smile.gif Are you trying to share your cable connection w/the other 2 systems or are you just trying to get the PC w/your net connection (from here on out I will call it the 'net PC) on to the LAN w/the other 2 systems?

If it's the first, you will need to add a NIC in your 'net PC - this will be for your LAN. Your LAN NIC needs to be assigned an IP and subnet mask of 192.168.0.1 and 255.255.255.0, respectively. You will need to use ICS (built-in to 98, 2k, and ME) or proxy soft, such as Sygate, to share your cable modem connection. Your clients need to be setup dynamically.

If it's the latter your trying to accomplish, you will still need to add a NIC to your 'net PC for the LAN. Set the IP and subnet of this NIC to 192.168.0.1 and 255.255.255.0, respectively. Use the same subnet mask on your other 2 systems and give one an IP of 192.168.0.2 and give the other an IP of 192.168.0.3.

In either case, you need to have File and Printer Sharing, and Client for Microsoft Networks bound to each of the "LAN NICs" and you need to share the drives/folders that you want to give access to on your LAN. Also, you need to use a diff log in name on each PC. I recommend you unbind File and Printer Sharing on the cable modem adapter. If your using Win2k, you will need to enable the guest acct. or create specific accts for LAN use.

Hope this helps.

[This message has been edited by glc1 (edited 11-03-2000).]

[richardc]

I am a little lost too, but I shall throw in my two cents anyway. Any chance that you have Netbeui installed on the others but not on the recently formatted one? I have found that while Netbeui is not always necessary, it sometimes helps when making a brand new connection.

[vyper2000]

Okay,

Let me refresh the scenario here. I use numbers to make things easier, so here goes.

1. I have 3 PCs.
2. All of them have a 10/100 NIC.
3. Before installed an external cable modem, all machines could see each other via Network Neighborhood.
4. I already assigned each machine its own IP address.
5. File and Printer Sharing was a success (had been for 4 years).
6. Ordered Cable net connection.
7. Tech came out.
8. Tech Attached Cable Box to Co-ax.
9. One RJ-45 cable was ran from the back of the Cable box to the UPlink port on my 5 port Syslink autoswitching hub.
10. Ports 1, 2, 3, each have a RJ-45 running from them to each of my machines.
11. The internet could not be accessed since I have the TCP/IP for my Ethernet card an IP address.
12. Tech on duty said I had to remove them.
13. Removed IP address from all 3 machines, and rebooted.
14. Each machine could then see the internet, as well as each other.
15. Time passed.
16. I reformatted one of my machines.
17. AFterwards, I ensured
A. IPX/Spx for Ethernet card was installed.
B. File and Printer sharing turned on.
C. Shared my two hard-drives and printer.
D. Selected "Disable Wins Res" in network.
E. Set up a computer name, and made sure workgroup name was the same as my other two PCs.
F. Rebooted via Client for MS Networks.
G. Windows 98 loads.
H. The net is accessed successfully.
I. Network Neighborhood only shows my machine.

Now, note that all machines have the same workgroup name. When I click "entire network" on my troubled PC, I can see other Charter Pipeline Customers' computers. I even see my workgroup name.

I click the work group name, and only my machine is seen.

I go to the other two PCs, do the same thing, and each time, my machine is not shown, but the two of them are under the workgroup I have setup.

Note: No proxy is needed for this peer-to-peer network since I'm using a hub with the external cable modem. Any machine can be powered down, and the others can still see the net.

Now, I'm seeking what I missed that is causing my machine to not see my other two machines. And, why can't the other machines see mine?

Thanks for the quick reply you previously gave, and thanks for your time,


Christopher Malone

[richardc]

I shall go with what I said. Also check out
viper2000's sage suggestions here: http://www.speedguide.net/ubb/Forum8/HTML/000650.html

[Rosco]

What other customers computers can you see?

Please explain this further
I don't beleive this is possible that you are seeing other people systems on your node within your network, the way you have it set up now.

To try and help, do you have the IPX protocol as your default or is it TCP/IP.
Make sure all systems match with the same protocol set as the defualt.

[vyper2000]

Yes sir/mam,

I can see other customers' PCs as well. I have worked at an ISP, so don't count me as a total idiot. I've already contacted Charter Pipeline about it, because I had expected only to see my other 2 PCs when I clicked on the Network Neighborhood. However, I saw many other computers that are used by customers of Charter Pipeline. Charter replied stating that the connections are all residing on the same network, different from 56k connections. I knew his point of view already, because working at the ISP I was at, in the office, clicking on Network Neighborhood, I could see many of the customer's PCs. So, it is possible, but that obvious stuff. That's where the saying "Cable users get hacked all the time" comes from. I've put many "readme.doc" notes on folk's desktops warning them of the situation, telling them to password protect their shared drives.

Thanks for your time,

Christopher.

Originally posted by Rosco:
What other customers computers can you see?

Please explain this further
I don't beleive this is possible that you are seeing other people systems on your node within your network, the way you have it set up now.

To try and help, do you have the IPX protocol as your default or is it TCP/IP.
Make sure all systems match with the same protocol set as the defualt.

[richardc]

OOPS - my apologies - I meant to say:
Also check out
glc1's sage suggestions here: http://www.speedguide.net/ubb/Forum8/HTML/000650.html

[CMcCollister]

Have you tried to ping each of your PCs from the each other and what were the results. Note: you may have to run winipcfg from each PC to see what IP address was assigned. When you run winipcfg note the subnet mask, as well. Are the three PCs within the same logical segment? (If you aren't sure how to check whether the PC IP addresses are on the same subnet let me know & I can walk you through it).

[vyper2000]

Great day,

I can't believe you folks can't see how I'm seeing the other customer's computers. I use ZoneAlarm so that none of them can hack mine. If you need additional proof, I'll be glad to send you a snap shot of my network neighborhood window that shows the "entire network." Drop by your local Cable ISP, and they will confirm what I am saying. If they deny it, it's for fear that you might be a hacker. If you are still in doubt, I'll be glad to send you directions to my residence. Any of you with PC Anywhere, I'll give you the IP address I'm at, then you can see for yourself.
Back to the issue at hand, yes, I have IPX/spx installed. I've always ensured it was installed so that I could play my Command and Conquer games with my home LAN. I'm still at a loss as to why my machine is not seeing my other two machines, but the other two can see each other. Yes, all machines have the same workgroup name, and all 3 have different ID names. Netbeui on and off didn't improve anything. It's a trivial thing for sure.

[CMcCollister]

How did the pings between the PCs work out?

It is possible that the new PC is using a different master browser than the other two that you built earlier. If that is so, then that would explain the different views of the network from the different PCs.

One more thing to try after you confirm the pings work. Take the rebuilt PC and use the Find feature and select Computer. Enter the IP address of one of your PCs that has sharing enabled. It should locate your other PC (this allows you to bypass the master browser as well as other netbeui issues).

If that works, open the discovered computer from the Find window and see if you can access resources. If this works then I would suspect a master browser issue. There are ways to work around that, especially since you have IPX/SPX enabled.

[toadvenom]

Are you sure that your network cards are properly bound to the same protocols? I found this site helpful: http://grc.com/su-bondage.htm

Are you able to see other cable customers in your Network Neighborhood because you are all using the same Workgroup name?

Also, I've found that when I first boot up, all my computers are networked but at some point in time, they loose their connection to each other, and I have to reboot to get them back together again. So, I'll be watching to see what your resolution is because it might shed light on my problem.
Thanks!

[quickfoot]

Make sure they have the same subnet mask, if they don't they won't see each other.

Also try mounting by the ip address as someone above said.

No one is debating your experience however all of us are volunteers and are troubleshooting your connection.

Please bear with us while we figure it out and try to remain calm http://www.speedguide.net/ubb/smile.gif

------------------
Microsoft Certified Systems Engineer

[cburgy]

Hi,
Make sure that all of your systems are on the same subnet. You can see the IP information but typing winipcfg from RUN or goto the command prompt and type ipconfig and look at the NIC adapter information (can get more by typing ipconfig /all). Make sure that your TCP/IP stack is set to be the default protocol (set under the network properties). Another thing to check is that NetBIOS over TCP/IP is enabled. This alows Microsoft's "wonderful" NetBeui protocol to be transported over TCP/IP. Windows can be really wierd about letting you see other systems. Reboot a couple of times as well.


------------------

Cheers,
Chris Burgy
Network Analyst
IT
Chevron

[vyper2000]

Hello there all,

Well, here's the moment some of you may have been waiting for. I know that I sure have. I failed to do the most obvious thing to correct a hardware issue. Well, it's one of them anyway. Before I spill the beans, I would first like to thank all of those that responded, and all of those that took the time to read my cry for help, but didn't have the answer to relay to me.
Okay, here's a refresher course. I could see the internet, but could not see my home LAN. Thus, I couldn't share my printers or files. Okay, I ensured that tcp/ip and netbeui and ipx/spx (most importantly) were installed. I also made sure that I had "file/print sharing turned on." Okay, I also went and made sure that all three machines had the same workgroup name. Oh yeah, by the way, in response to a question about that issue listed above - no - I was seeing folks that had different work groups than I did. Okay, you already know the reboots I encountered, etc. I even changed to a different port on my 10/100 HUB that I have connected to my Cable Modem (external). Well, as you already know, none of that or any of the other ideas provided did any good.
Okay there Microsoft techie who responded to my help cry. I'm tickled that you missed this one, because everything I had a hardware issue in the past (before I learned anything) Microsoft was always telling me to do this.
Now to the conclusion. I decided to power my machine now, and just relocated my PCI Ethernet card to another slot. I did just that, blew out a few dust bunnies, and booted my baby back up. Once all my essentials were loaded, I sat back in my chair and click that dreaded "network neighborhood" icon once more. To my satisfaction, I saw my other two machines listed in there. Talk about doing the dance of joy. I was about to head out and just buy another Cat45 cable, and go from that point to replacing other hardware since I had exhausted what I thought was every software tweak I could find, and utilitize provided from you good folks. It just took a simple card relocation to solve this trivial pursuit quest of mine.
You see, my other machine has a tendency to lose contact with it's Ethernet card. So, I would just move it to another slot. Since I was already seeing the internet with this machine, I didn't think to relocate the card until just a few minutes ago. Yes, as soon as I got it to work, I came straight here to shout the good news.
Some of you may think I might have lost my cool in early messages. Please forgive me on that. I'm so used to providing help in this area, that I was frustrated to have to troubleshoot my own machine. My apologizes to you, and my thanks to you as well.

You good folks have a great day/night,

Thanks a million for your help,

LAN born again,

Christopher Malone
cmalone@techie.com
cable_cruncher@hotmail.com

[DaveM]

You really should unbind File and Printer sharing from TCP/IP !!!

Leave it bound on IPX or NetBeui, this will still allow your local computers to see each other, but should disallow others on "your cable system" from seeing your workgroup.