Home LAN with 2 Win2k machines.
Thread Starter
Joined: Jul 2005
Posts: 82
Likes: 0
From: Lv426
Home LAN with 2 Win2k machines.
Now that one of the sproglets has a stack in her bedroom I've been trying to network the 2 machines together...
Bought a crossover cat5e cable thinking this would be 5 minutes work, however it was not to be...
Neither machine can find the other on the network despite both sending and receiving packets from each other. I've set mine as host and hers as guest with respective IP addresses of 192.168.1.2 and 192.168.1.3. Both are looking for the same workgroup and both appear under their respective network places.
There was a piece on microsoft's website which mentioned that crossover cables are not explicitly supported under the protocol which is a bit worrying, though the chaps and chapesses in the shop were quite insistent.
Does anyone have a noddy guide available which shows how to do this?
Sprogletesses machine was a present which had previously been used on a network. Maybe this is part of the problem...
How embarrassing......
Bought a crossover cat5e cable thinking this would be 5 minutes work, however it was not to be...
Neither machine can find the other on the network despite both sending and receiving packets from each other. I've set mine as host and hers as guest with respective IP addresses of 192.168.1.2 and 192.168.1.3. Both are looking for the same workgroup and both appear under their respective network places.
There was a piece on microsoft's website which mentioned that crossover cables are not explicitly supported under the protocol which is a bit worrying, though the chaps and chapesses in the shop were quite insistent.
Does anyone have a noddy guide available which shows how to do this?
Sprogletesses machine was a present which had previously been used on a network. Maybe this is part of the problem...
How embarrassing......
Joined: Jan 2005
Posts: 20
Likes: 0
From: Sittingbourne
Try another cable, it wouldn't be the first time someone picked up a normal cable thinking it was a crossover.
I don't use windows firewall, but if your machines don't have a connection to the internet, switch it off - the firewall may disable discovery of the machine. If you are connected to the internet however, I wouldn't recommend it.
If you know someone with a hub, try testing with that.
Check that the machines can ping each other, click start...run and type cmd. In the command window, type
ping <other ip address>
and see if you get reply messages.
Also, type ipconfig /all on each machine and let us know the output.
I don't use windows firewall, but if your machines don't have a connection to the internet, switch it off - the firewall may disable discovery of the machine. If you are connected to the internet however, I wouldn't recommend it.
If you know someone with a hub, try testing with that.
Check that the machines can ping each other, click start...run and type cmd. In the command window, type
ping <other ip address>
and see if you get reply messages.
Also, type ipconfig /all on each machine and let us know the output.
Thread Starter
Joined: Jul 2005
Posts: 82
Likes: 0
From: Lv426
Well the cable dosn't specifically have crossover marked on it but it did come from a packet marked as Crossover Cable Cat.5e UTP 10m.
Ping works fine, with or without the firewall loaded.
Ipconfig /all results in a window that shuts down so quickly that it is impossible to tell what the results were.
Looks as though the problem is sorted...
Hint on usenet suggested that one needed to have the same users set up on each PC running 2000.
After setting up the users on Holly\'s machine (with the same passwords) her machine was visible....
Gawd knows why the users need to be the same on each machine.........
Ping works fine, with or without the firewall loaded.
Ipconfig /all results in a window that shuts down so quickly that it is impossible to tell what the results were.
Looks as though the problem is sorted...
Hint on usenet suggested that one needed to have the same users set up on each PC running 2000.
After setting up the users on Holly\'s machine (with the same passwords) her machine was visible....
Gawd knows why the users need to be the same on each machine.........
Joined: Sep 1998
Posts: 513
Likes: 0
From: Sydney, Australia
When you want to use ipconfig, open a command window first.
Not sure about Win 2k, but in XP - Start, Run, type "cmd" or "command" (without the qotes) in the window, then Enter or OK.
That will open a black command line window.
From there you can type ipconfig or any other DOS-like commands and see the output without the window closing.
AA
Not sure about Win 2k, but in XP - Start, Run, type "cmd" or "command" (without the qotes) in the window, then Enter or OK.
That will open a black command line window.
From there you can type ipconfig or any other DOS-like commands and see the output without the window closing.
AA
Joined: Mar 2004
Posts: 133
Likes: 0
From: Glasgow
Spinflight,
Maybe I am teaching you to suck eggs, but have you actually enabled sharing on the drives of both pc's?
If you are still having problems send me a pm and i will give you my number and we can chat
Mike
Maybe I am teaching you to suck eggs, but have you actually enabled sharing on the drives of both pc's?
If you are still having problems send me a pm and i will give you my number and we can chat
Mike
Thread Starter
Joined: Jul 2005
Posts: 82
Likes: 0
From: Lv426
Thanks for the help lads, the problem be sorted though.
I posted as such earlier but as it followed one of my other posts it just editted the first.
Problem was that myself and Holly had different users set up on each machine. Once I set up the users to be the same, with the same password, it worked fine.
A few bottles of Shiraz probably didn't help either.
I posted as such earlier but as it followed one of my other posts it just editted the first.
Problem was that myself and Holly had different users set up on each machine. Once I set up the users to be the same, with the same password, it worked fine.
A few bottles of Shiraz probably didn't help either.
