Networking with Windows XP

How are you connecting them? USB cable, Ethernet cable or a router?

Normally you just connect both PC's via your chosen method and then reboot... Make sure that any files and folders you want made available on your "network" are set to "shared" status.
When you go into "My Network Places" you should then be able to add the other PC to your list. (and vs versa) :wink:
 
Upvote 0

KM-Tiger

Free Member
Aug 10, 2003
10,346
1
2,893
Bexley, Kent
The trouble with Windows P2P networking is that it can drive you mad when it doesn't work. Resist the temptation to throw the PC's through the nearest window!

There is a wealth of information here:-

www.wown.info

or you could try posting your question on this forum, where there are a lot of knowledgeable people:-

http://bbs.adslguide.org.uk/postlist.php?Cat=&Board=multiuser

The most common reason for file sharing not working is a firewall, do either of the PC's have a firewall?
 
Upvote 0
ok
what is the purpose of the network? file/print sharing? or just internet sharing?
Can either/both pc's get online through the router at the moment?
Most SOHO routers are configured to assign IP addresses/dns details by default, are your clients (the 2 pc's) picking up an ip from the router? (click start, run, on the dos box type ipconfig /all) post back details so far and we'll take it from there.
 
Upvote 0

cjd

Business Member
  • Nov 23, 2005
    15,996
    3,433
    www.voipfone.co.uk
    Can both PCs see the internet?

    That bit usually just works, it's the file sharing and work groups that usually cause the problem and it's almost always down to firewalls, incorrect setting of permissions and workgroups.

    By far the simplest approach is to use the Windows network set up wizard.

    Start.....my compter.....my network places........setup a home or small office network.

    then go to windows help and follow the instructions on file sharing.
     
    Upvote 0
    I'd disagree on using the setup wizard if the router is configured as a DHCP server which it probably is, might end up with IP conflicts, not to mention the fun and games you MAY have if you need to run the wizard again. Its not difficult at all to setup manually, and if things go wrong, (which they shouldnt) afterwards then you know what to change to put it right.
     
    Upvote 0

    cjd

    Business Member
  • Nov 23, 2005
    15,996
    3,433
    www.voipfone.co.uk
    Strange - I have set-up 5 or six networks in the last couple of years and had no problem at all using the wizard.

    I would suggest that anyone needing to ask advice about how to do it will struggle to get to grips with a manual configuration.

    Windows expects DHCP because that's how pretty much every domestic SOHO router works and handles it every time for me, maybe I just got lucky ;-)
     
    Upvote 0
    personally I think you just got lucky ;)
    the network wizard does work when it wants to, but as I mentioned, you have no clue what its changed, and that being the case, how to troublehoot should it stop working, not to mention enabling the guest account for you !(I think they fixed this in SP2 but not 100% sure)
    The problem is, like anything else, people always "manage to get it working" but working, and working properly arnt always the same, I presume from your sig that you are somthing to do with (owner?) of voipfone, its a bit like someone telling you that they have skype so they dont need a voip solution.

    Hope that makes sense lol
    Windows expects DHCP because that's how pretty much every domestic SOHO router works
    Not sure what you mean by that, as far as I remember every version of windows has always configured all network adaptors to "expect" to recieve and IP/gateway/dns from a DHCP server, much before the average jo bloggs could afford a router.
    Anyway, if ohanlonj has a go at setting it up any which way and gets stuck, then I'm sure we'll sort him/her out between us !
     
    Upvote 0

    KM-Tiger

    Free Member
    Aug 10, 2003
    10,346
    1
    2,893
    Bexley, Kent
    confused said:
    .............. as far as I remember every version of windows has always configured all network adaptors to "expect" to recieve and IP/gateway/dns from a DHCP server..................
    True that's the default setting, but it can easily be changed, often by people trying to "help".

    The real weakness of Windows as a DHCP client is that it doesn't give an error message when DHCP fails. Instead it falls back on APIPA and you end up with a useless 169.xxx.xxx.xxx address and no gateway, and absolutely no idea why nothing works. Your average user doesn't know about "ipconfig -all" from the command line to find out.
     
    Upvote 0
    hi,

    XP will actually give you a balloon saying theres limited or no connectivity, however theres no real reason for it to give an error ? why should it ? ipconfig in various forms has been available since '95/NT days. One disadvantage of using DHCP on a small network is as you mention is APIPA, at least if you assign static IP's then you can troubleshoot, if you have a 169.254.x.x ip then you cant do a great deal, apart from manually asign a static ip and snm to put it on the same network as the rest.....
    I agree that "people trying to help" can often cause problems, often caused by ill advice or little knowledge. I do hope you dont think I am one of those.
     
    Upvote 0

    cjd

    Business Member
  • Nov 23, 2005
    15,996
    3,433
    www.voipfone.co.uk
    I don't think we're helping much :-(

    As a first step I suggest you try the wizard after that it gets trickier but we'll unpick it in the end.
     
    Upvote 0

    Latest Articles

    Join UK Business Forums for free business advice