1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Networking Blues

Discussion in 'Networking (Hardware & Software)' started by skun999, 2006/12/27.

  1. 2006/12/27
    skun999

    skun999 Inactive Thread Starter

    Joined:
    2006/12/27
    Messages:
    3
    Likes Received:
    0
    I have 4 computers connected to my network and I understand why 1 can't be seen, but I have no idea why one won't. I have a main router (Siemens) which is wired directly to one computer (XP HOME 1) which is given a DCHP automatically. I then have it wired to another router (Lynksys) which is only acting as a switch (the it is connected via one of the LAN ports not WAN, and DCHP is disabled). From this "switch" I have two computer connected (XP MEDIACENTER) and (XP PRO). I also have a fourth computer (XP HOME2)which is connected wireless to a third router (BELKIN), but since the DNS and Gateways are different I can see why it can't be seen as a workgroup computer in MSHOME. (This router is connected to the Siements via WAN port, but I gave it a static IP WAN address within the range of the Siemens so it works fine, i could make it a wireless access point only, but it works as is, so I leave it).

    After all that, here is my problem, my XP MEDIACENTER can see and access the XP HOME1 computer, but the XP HOME1 computer cannot see or access any computer and neither can the XP PRO computer.

    The only thing I can reason for this is that the XP MEDIACENTER and the XP HOME1 are not password protected logins, whereas the XP PRO is, but I don't understand why the XP HOME1 cannot see the XP MEDIACENTER.

    To add more info, if needed. When XP HOME1 and XP HOME2 were connected via a legitimate switch, then later the Lynksys, they could both see and access eachother.

    I know this is a lot of information, but I thought I'd give as much as I could upfront.
     
  2. 2006/12/27
    skun999

    skun999 Inactive Thread Starter

    Joined:
    2006/12/27
    Messages:
    3
    Likes Received:
    0
    i'd also like to mention that i can ping the XP HOME1 from XP MEDIACENTER via the name and ip, the XP HOME1 from XP PRO via ip only, the XP PRO from XP MEDIACENTER via ip only. Neither computers can ping XP MEDIACENTER (ip or name) and all can ping the router (SIEMENS). I don't know if that helps. Also the XP PRO is static, while the XP HOME1 and XP MEDIACENTER are assigned by DHCP.
     

  3. to hide this advert.

  4. 2006/12/28
    Bill Castner

    Bill Castner Inactive

    Joined:
    2006/08/30
    Messages:
    1,980
    Likes Received:
    0
  5. 2006/12/28
    visionof

    visionof Inactive

    Joined:
    2006/11/12
    Messages:
    778
    Likes Received:
    5
    Why such a complex setup ?
    If it is difficult for you to explain simply then lots of luck.
    With such a complex setup you are asking for problems.
    Simplify the network so you can go down to a simple baseline in order to isolate networking problems.
    Networking is difficulting enough without adding stumbling blocks in your path.
     
  6. 2006/12/28
    Bill Castner

    Bill Castner Inactive

    Joined:
    2006/08/30
    Messages:
    1,980
    Likes Received:
    0
    I admit it looks unecesarily complicated, but you see LANs grow this way all the time. (I am, by the way, not recommending it).

    You start with one PC connected to the broadband modem.
    You want to add a second PC, so you add a router.
    You then want to add additional PCs, and do not want to star wire every PC to the existing router, so you run one cable to the Linksys in this case to be used essentially as a switch.
    Finally, you want a machine isolated from the LAN (for security concerns) that also happens to be wireless. The puzzle is complete.

    If you could start with a blank piece of paper, this of course is not what you would draw.

    One important thing I forgot to note above: Disable the DHCP server on the Belkin. It is not needed and could potentially mess things up as you cannot have two DHCP servers on this LAN. Remember that DHCP requests are handled by Broadcasts, so the subnetting is not a bar to the Belkin responding with DHCP service to other clients as you now have it configured. The Broadasts would be made through the common point -- the Siemens router.
     
  7. 2006/12/29
    skun999

    skun999 Inactive Thread Starter

    Joined:
    2006/12/27
    Messages:
    3
    Likes Received:
    0
    Thanks for the link, I can view other computers on my XP PRO but still cannot access, however. I think it is the login without password problem, which I will try to resolve later.

    In answer to the questions of why my system is so complicated is because I live i a large complex. All rooms are wired with CAT5, but only 1 connection. It happens that we have 2 rooms with 1 computer each, which would work fine using 1 router, but one is nowhere near the connection (hence the wireless). Also the 3 room has two computers. Since I am already in the possession of 3 routers (from other places) I intended to use one as a switch instead of buying a switch. I wireless network will not reach all computers, and only 2 have wireless cards anyways. So that explains that situation. I have not tried anything else yet, minus that quick fix in TCP setting. Any other suggestions are appreciated.
     
  8. 2006/12/30
    Bill Castner

    Bill Castner Inactive

    Joined:
    2006/08/30
    Messages:
    1,980
    Likes Received:
    0
    For the XP Pro that can see and not access:

    Control Panel, Folder Options, View
    scroll near the bottom and checkmark to enable 'Use simple file sharing - recommended'

    That should be all you need to do.

    But see my checklist at point #14 in this thread: http://www.windowsbbs.com/showthread.php?t=60063
     
    Last edited: 2006/12/30

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.