the set-up is 2 machines, one running windows xp home and the other running xp pro. both have standard ethernet cards in working condition. they are connected to each other, directly, with a standard ethernet crossover cable. both machines are set up to recognize each other care of MS' home networking wizard. one machine has an internet connection, which is shared to act as the ICS host.
the problem is that this network is rather erratic. when booted up, both machines recognize each other without a problem, and i'm told that the network is functioning. also, the non-internet one recognizes the active internet connection in its Network Connections folder, and lists the connection duration and speed. however, no program seems able to connect to the internet from the non-internet one. also, whenever either computer is instructed to view the other's shared folders, explorer locks up and crashes.
moreover, this doesn't always happen. sometimes, the network works perfectly, with very fast transfers, and no lock ups. this only seems to happend when both computers have been off for a period of time, and if one is rebooted, the problems persist. as you can imagine this is very annoying, so if anyone has any ideas of the causes or solutions please do tell me (short of migrating to another OS). ta.
First of all you have of course updated both computers with latests updates like Service Pack 1 and any critical update after that.
Second of all you are certain you have set up the Networking wizard correct so for instance Firewire is a not valid gate for the internet and so the computer with internet connects only through the right source and shares it connection with others (bridge to the right Ethernet card) ... also the other computer is of course set up to only connect through the right (ethernet) card and get its ressources automatically.
Then remember the computer with the internet connection should be turned on first so the second one can get its lan ressources (ip, gateway, etc) from the one with internet. Should the computer without internet be on first, then Windows will simply apply an ip adress for the ethernet card (since the other computer is off). Deactivate and activate the connection or use the Repair option to force windows to get an automatic ip adress when the one with internet is started.
Windows network is generally slow and stupid. Pinging each other often speeds up the registration of the computers so you can see each other in "neighbour computers" or what ever its called in english. Also make sure you are in the same workgroup. If its working too bad simply use ftp instead. Its both faster and better.
My uncle has a similar problem. He has an XP laptop, and a win98 desktop. The XP laptop will not recognize the win98 desktop is there(and won't send files to it/use its connection), but the XP laptop miraculously accepts all transfers from "nowhere"(the 98 desktop).
Another example of how Windows XP sucks. Update to Windows 98 SE today! (or win2k PRO)
no matter how microsoft want to make windows easier to use networking will always remain one of the hardest setup thingies...
all i did was plug my 2 computers together with a standard cat5 cable (i think it is) and clicked on the network wizard, did it all for me. but you've probably already tried that and yea ill shuttup now
Those hubs are cool. A cyber cafe right in your very home, with your favorite games...
If only my second computer hadn't blown up last week.
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
I have the same problem. My girlfriend has her computer running WinXP home, and mine running XP Prof. Both computers are connected to a switch.
The computers can see each other in the network thing, but can't access each other. So if we wanna transfer stuff we have to use msn (msn transfers through a network connection if one is present), and archive things first. Also, we can play network games together...it's just pretty damn irritating though...
i think it might be a problem with XP home, cuz i tried another ethernet adaptor on her computer and it didn't do any good.