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

Trouble accessing file/printer shares

Discussion in 'Networking Issues' started by ralphb, Sep 3, 2005.

  1. ralphb

    ralphb Network Guru Member

    I hope this is not a stupid question, but I have a problem I hope you can help me with. I have the approximately the following setup:

    Cable Modem
    Wired NAT Router
    ¦ ¦ ¦ ¦
    ¦ ¦ ¦ \-- Wired W2K PC with shared files & printer
    ¦ ¦ ¦
    ¦ ¦ \----- Another Wired W2K PC with shared files
    ¦ ¦
    ¦ \------- Linux SAMBA server
    Linksys WRT54gs WLAN Router ~~~~ WiFi W2K Laptop PC

    Now, the wired PCs have no trouble seeing each other's shared files & printer and the SAMBA shares. However, the WiFi Laptop PC can see only the SAMBA shares, but not the W2K PCs or their shared resources.

    I thought this might be down to port forwarding of the NetBEUI services (ports 137..139?). I couldn't get the port forwarding settings to stick on the standard Linksys firmware, so upgraded to the HyperWRT 2.1b1. However, I still can't get the laptop to see the wired computers and/or their resouces.

    Can anyone advise me what I might be doing wrong here. And what to do to fix it.

    Thanks in anticipation.

  2. ralphb

    ralphb Network Guru Member

    Hmm, I've found I can get around the problem by modifying the hosts file on the laptop to resolve the names of the wired PCs to the ip addresses. However, I'm left wondering why, if the wired NAT router can (presumably) provide name services for the wired PCs then why can it not do the same for the laptop via the WLAN router?

    Since all the PCs are using DHCP, modifying the host file is not the perfect solution, but I can't come up with a better idea just now. Can anyone here?

  3. audiophile

    audiophile Guest

    These pointouts might not be neither something you don't want to configure your network :sadbye: or unrelevant but what the hey. I'll give it a try. :)

    1. I recommend you to use static ip's or configuring a mac-validation to your dhcp and then be using ip-addresses instead of networik names.
    2. If your using a domain, a DNS's are required. Thought you would have problems loggin in.

Share This Page