#1
  1. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2004
    Posts
    5
    Rep Power
    0

    Networking windows xp home with windows xp home


    Hello,

    I am having a problem sharing files/folders from one windows xp machine with another. Please see below:
    The router is a linksys 4 port plus wireless access point.


    Machine A
    ---------------
    Windows XP
    Wired to Router
    Can go to internet
    Can "ping" "machine B"
    Not DCHP; static address (192.168.1.100)
    Has same DNS, gateway settings as machine B
    gateway settings as Machine A
    Can view shared folders on Machine B


    Machine B
    ---------------
    Windows XP
    Wireless to router
    Can go to internet
    CanNOT "ping" "machine A"
    Not DHCP; static address (192.168.1.111)
    Has same DNS, gateway settings as Machine A
    CanNOT view shared folders on Machine A


    Does anyone have any ideas?
    THANK YOU!
    Peter.
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Regular (2000 - 2499 posts)

    Join Date
    Aug 2003
    Posts
    2,491
    Rep Power
    19
    Hi pdelucia!

    This is a checklist I use! Any comments graciously welcomed!

    Both machines have matching user accounts and passwords and users logged in.

    Both machines have different computer names (use simple names with no spaces).

    Both machines have the same workgroup name. (such as: workgroup)

    At least one computer has shared files or folders.

    Machines are connected via: crossover cable, hub, switch or router.

    Both machines have TCP/IP installed.

    Both machines have the same IP addressing scheme.

    Example: 192.168.0.10 and 192.168.0.11

    Both machines have the same subnet mask

    Example: 255.255.255.0

    If using a router, the Default Gateway should be set to 192.168.0.1.

    Note: if using a router, DHCP will issue an IP address and a subnet mask automatically. Just have “obtain an IP address automatically” checked in the TCP/IP properties.

    These both can be easily checked by:
    Example for XP: Start > All Programs > Accessories > Command Prompt > ipconfig /all

    Example for Windows 9x: Start > Programs > MsDos Prompt > winipcfg

    Both machines have File and Printer Sharing turned on.

    Commercial firewalls on both machines should be configured with trusted IP addresses. Or disable firewall (not recommended).

    Example: 192.168.0.10 and 192.168.0.11

    If using XP's built-in Firewall: go to Start > Control Panel > right-click Network Connections > Properties > Advanced > Settings > Services > Add > enter File Sharing for the description > enter 127.0.0.1 for the IP address > enter 445 for both Port numbers > make sure the TCP radio button is selected > click OK > put a checkmark next to the new service to enable it .

    Can you ping the local loopback address on each machine?

    Example for XP: Start > All Programs > Accessories > Command Prompt > ping 127.0.0.1

    Example for (Windows 9x): Start > Programs > MsDos Prompt > ping 127.0.01

    If you receive “request timed out”, you have TCP/IP configuration problems, incorrectly installed or defective network card (NIC).

    Can the computers ping each other?

    Example from the 192.168.0.10 machine: ping 192.168.0.11

    If not, you have connectivity problems (cabling, hub, firewall blocking, etc).

    Tom
  4. #3
  5. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2004
    Posts
    5
    Rep Power
    0
    thank you for repsonding.

    what is driving my crazy is that I can ping machineB from machineA, but I canNOT ping machineA from machineB....

    One thing I can think of is that machineB is using a wireless connection. But, I have even tried using DCHP and it connects to the DHCP server (the router) fine and gets an IP address. I switched to static IP addresses to just see if it would make a difference...

    machineB still cannot ping machineA

    Can you think of anything else to try?
    Thanks,
    Peter.
  6. #4
  7. No Profile Picture
    Contributing User
    Devshed Regular (2000 - 2499 posts)

    Join Date
    Aug 2003
    Posts
    2,491
    Rep Power
    19
    Have you tried using a different channel on your wireless router?
  8. #5
  9. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2004
    Posts
    6
    Rep Power
    0
    k, the only things on the checklist, are, they cant ping each other.
    and they dont ave same user accounts.
    what do u mean by this? On XP <-> XP they dont need same accounts.
  10. #6
  11. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2004
    Posts
    5
    Rep Power
    0
    nope..haven't tried a different channel on the wireless router. but machineB can go to the internet just fine..it all works except NOT being able to see machineA.

    I can't see why this wouldn't work.. but it doesn't...
  12. #7
  13. No Profile Picture
    Contributing User
    Devshed Regular (2000 - 2499 posts)

    Join Date
    Aug 2003
    Posts
    2,491
    Rep Power
    19
    As far as the textbooks are concerned you dont need matching user accounts, but it improves connectivity, go figure?

    Tom
  14. #8
  15. No Profile Picture
    Contributing User
    Devshed Regular (2000 - 2499 posts)

    Join Date
    Sep 2003
    Location
    Oregon
    Posts
    2,157
    Rep Power
    933
    Firewall. Disable the XP firewall.

    I can't tell you how many hours I spent the first time only to discover it was Zone Alarm that was blocking me.

    I have 12 years in networking from 8088's to VMS Alpha servers.

    Boy did I feel dumb!
  16. #9
  17. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2004
    Posts
    5
    Rep Power
    0
    I tried disabling XP's default firewall too..
    damm!! there has got to be something stupid I am missing...
    there has to be a reason why I can't even PING the only machine, but name OR ip address......

    maybe the network card is bad????
  18. #10
  19. No Profile Picture
    Contributing User
    Devshed Regular (2000 - 2499 posts)

    Join Date
    Aug 2003
    Posts
    2,491
    Rep Power
    19
    ping 127.0.0.1 willl tell you if the NIC is bad.
  20. #11
  21. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2004
    Posts
    5
    Rep Power
    0
    I will try that.. thanks... the machines are at the office - not where I am now - I will definitely try that.. I am pretty sure pinging 127.0.0.1 has worked tho...

IMN logo majestic logo threadwatch logo seochat tools logo