1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

More PC's can't see each other

Discussion in 'Networking Issues' started by luchkow, Nov 29, 2004.

  1. luchkow

    luchkow Network Guru Member

    Good evening,

    On Nov 19, Thom D posted a topic entitled "PC's can't see each other" about his computers that could connect to the internet etc. and could ping each other, but couldn't make use of file or printer sharing.

    Did anyone have a solution? (It just seemed like the thread ran out.)

    I have had exactly the same problem:

    WRT54G V.2
    Computer 1 (desktop) connected with cable
    Computer 2 (laptop) wireless
    both running XP pro
    Router firmware - Satori 4.0g

    In then end I have reflashed my router with WRT54GV2_3.01.3_US_code from Linksys and Alla Peanutbutter Sandwitches... (lightning...) everythings works just like magic.

    The one difference: with the Linksys firmware my wife (laptop) can log on to my computer (and printer) without needing her username/password to my computer (desktop). With Satori however, she was prompted for a username and password which then never worked. She just kept being presented with a clear login dialogue...

    Does anyone have any thoughts about this?

  2. Esquire

    Esquire Mesquire Staff Member Member

    I don't know about the login issue with the Satori firmware you described - I haven't come across anything like this in my brief encounter with the firmware, but on the file and printer sharing, here's what I do, which hasn't failed me so far :p

    1. Force NetBIOS to enable on each client.
    Go to Network Connections, right click your Local Area Connection or Wireless Network Connection, and select Properties.
    Select Internet Protocol (TCP/IP) and click [Properties], then click [Advanced].
    Go to WINS and enable NetBIOS.


    2. Identify each client on the network
    Make sure the Computer Name for each computer is UNIQUE on your network. You can check each client's Computer Name by right-clicking My Computer on your Windows Desktop and select Properties then go to Computer Name tab. You can also access the same Properties screen via System icon in Control Panel. Give a new Computer Name to any client you found not to be unique. You will need to reboot for any changes to take effect.

    Ideally, WORKGROUP should also be the same, but on Windows XP, this isn't necessary, and in any case the default WORKGROUP name is typically called WORKGROUP (how original!) and is the same on any Windows 2000/XP computer unless it has been changed.

    3. Configure firewall running on your clients
    If you are using Internet Connection Firewall (ICF) on pre-SP2 Windows XP, the easiest is to disable ICF. If you wish to leave ICF on, you need to open the following ports to IP address
    UDP 137
    UDP 138
    UDP 445
    TCP 139
    TCP 445

    If you are using Windows Firewall (Windows XP SP2), you can simply enable File and Printer Sharing in the Exception section of the firewall configuration, which you can access via the Windows Firewall icon in Control Panel.

    You will need to consult the software's help file on configuring other firewall applications, but for ZoneAlarm, the network must be placed in Trusted zone. I find the default Internet zone blocks File and Printer Sharing.


    4. Share folders and printers to the network.
    Typical examples of setup.
  3. 4Access

    4Access Network Guru Member

    Very nice tutorial Esquire! But in luchkow's case I think the answer is much more simple. The big tip is that it works with other firmware but not Sveasoft's Satori... Which just happens to enable a somewhat strange feature by default:

    Good luck. ;)
  4. Esquire

    Esquire Mesquire Staff Member Member

    Hahaa. I don't remember seeing the Loopback option during the few days I was trying the firmware - must have disabled it without realizing.
  5. luchkow

    luchkow Network Guru Member

    Hi Folks,

    Thanks for taking the time to respond in such detail.

    In my travels, I had disabled the loopback, as I had seen this suggestion in another post. It rectified something else that was happening but I don't remember what it was. (Thus is the state of my brain - always sieve like...) Anyhow, this was the state (loopback disabled) in which my problems were occuring.

    The laptop in question is not in the house at the moment so I can't try out anything new. I will do so in the next day or two and see if I can't find anymore clues.


Share This Page