PDA

View Full Version : Problems networking with XP pro computers


Psymaster
January 9th 04, 10:58 PM
I have two computers which I have connected with a 20m
crossover cable via their on-board network cards. I configured
them to have different names and the same workgroup name, but
there are problems. Even though i managed to share some
folders and both computers can see the other one's files and
sometimes copy them, this is impossible with bigger files.
Creating network places is a pain, too, because it requires
entering the address manually, because browsing doesn't work
(results in a hang).

Playing multiplayer works quite reliably in civilization 2 for
instance, but not very well on other games.



After checking that the XP firewall is disabled, I did some
tests using the PING command. Now, I don't have any experience
with networking and I don't know how much packet loss is
acceptable, but I got results like this:

4 bytes packet: 2% loss
8 bytes packet: 3% loss
32 bytes packet: 6% loss
256 bytes packet: 17% loss
512 bytes packet: 22% loss


All tests with ~100 packets or more.


So, what seems to be the problem, is it software or isn't it?
Both network cards are new, and the cable brand new as well.
Any suggestions would be vastly appreciated.

GB
January 9th 04, 10:58 PM
Hi,

your cross over cable is too long, if you cannot affor a hub/switch, use a
normal cat5 cable and a shorter cross-over (1m or 3ft) coupled to a
female-to-female cat5 adaptor.

I am 99.9% confident this will cure your network ailments.

Regards

GB
"Psymaster" > wrote in message
...
> I have two computers which I have connected with a 20m
> crossover cable via their on-board network cards. I configured
> them to have different names and the same workgroup name, but
> there are problems. Even though i managed to share some
> folders and both computers can see the other one's files and
> sometimes copy them, this is impossible with bigger files.
> Creating network places is a pain, too, because it requires
> entering the address manually, because browsing doesn't work
> (results in a hang).
>
> Playing multiplayer works quite reliably in civilization 2 for
> instance, but not very well on other games.
>
>
>
> After checking that the XP firewall is disabled, I did some
> tests using the PING command. Now, I don't have any experience
> with networking and I don't know how much packet loss is
> acceptable, but I got results like this:
>
> 4 bytes packet: 2% loss
> 8 bytes packet: 3% loss
> 32 bytes packet: 6% loss
> 256 bytes packet: 17% loss
> 512 bytes packet: 22% loss
>
>
> All tests with ~100 packets or more.
>
>
> So, what seems to be the problem, is it software or isn't it?
> Both network cards are new, and the cable brand new as well.
> Any suggestions would be vastly appreciated.

Steve Winograd [MVP]
January 9th 04, 10:58 PM
In article >, "GB"
> wrote:
>"Psymaster" > wrote in message
...
>> I have two computers which I have connected with a 20m
>> crossover cable via their on-board network cards. I configured
>> them to have different names and the same workgroup name, but
>> there are problems. Even though i managed to share some
>> folders and both computers can see the other one's files and
>> sometimes copy them, this is impossible with bigger files.
>> Creating network places is a pain, too, because it requires
>> entering the address manually, because browsing doesn't work
>> (results in a hang).
>>
>> Playing multiplayer works quite reliably in civilization 2 for
>> instance, but not very well on other games.
>>
>> After checking that the XP firewall is disabled, I did some
>> tests using the PING command. Now, I don't have any experience
>> with networking and I don't know how much packet loss is
>> acceptable, but I got results like this:
>>
>> 4 bytes packet: 2% loss
>> 8 bytes packet: 3% loss
>> 32 bytes packet: 6% loss
>> 256 bytes packet: 17% loss
>> 512 bytes packet: 22% loss
>>
>>
>> All tests with ~100 packets or more.
>>
>>
>> So, what seems to be the problem, is it software or isn't it?
>> Both network cards are new, and the cable brand new as well.
>> Any suggestions would be vastly appreciated.
>
>Hi,
>
>your cross over cable is too long, if you cannot affor a hub/switch, use a
>normal cat5 cable and a shorter cross-over (1m or 3ft) coupled to a
>female-to-female cat5 adaptor.
>
>I am 99.9% confident this will cure your network ailments.
>
>Regards
>
>GB

I don't think that the crossover cable is too long, GB. The maximum
Ethernet cable length is 100m, and Psymaster's cable is only 20m long.

However, it's quite possible that the crossover cable is sub-standard,
especially if it's home-made. It might also be picking up
electromagnetic interference from electrical wiring, appliances, etc.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

GB
January 9th 04, 10:58 PM
Hi Guys,

I had a similar problem on a small LAN, where they used a similar cross over
length and also spoke to my cable technician, and he suggested the above,
which did the trick even though cable connectors are not really recommended
due to signal loss, but we are not talking about mission critical stuff
here...

Regards

GB
"Steve Winograd [MVP]" > wrote in message
...
> In article >, "GB"
> > wrote:
> >"Psymaster" > wrote in message
> ...
> >> I have two computers which I have connected with a 20m
> >> crossover cable via their on-board network cards. I configured
> >> them to have different names and the same workgroup name, but
> >> there are problems. Even though i managed to share some
> >> folders and both computers can see the other one's files and
> >> sometimes copy them, this is impossible with bigger files.
> >> Creating network places is a pain, too, because it requires
> >> entering the address manually, because browsing doesn't work
> >> (results in a hang).
> >>
> >> Playing multiplayer works quite reliably in civilization 2 for
> >> instance, but not very well on other games.
> >>
> >> After checking that the XP firewall is disabled, I did some
> >> tests using the PING command. Now, I don't have any experience
> >> with networking and I don't know how much packet loss is
> >> acceptable, but I got results like this:
> >>
> >> 4 bytes packet: 2% loss
> >> 8 bytes packet: 3% loss
> >> 32 bytes packet: 6% loss
> >> 256 bytes packet: 17% loss
> >> 512 bytes packet: 22% loss
> >>
> >>
> >> All tests with ~100 packets or more.
> >>
> >>
> >> So, what seems to be the problem, is it software or isn't it?
> >> Both network cards are new, and the cable brand new as well.
> >> Any suggestions would be vastly appreciated.
> >
> >Hi,
> >
> >your cross over cable is too long, if you cannot affor a hub/switch, use
a
> >normal cat5 cable and a shorter cross-over (1m or 3ft) coupled to a
> >female-to-female cat5 adaptor.
> >
> >I am 99.9% confident this will cure your network ailments.
> >
> >Regards
> >
> >GB
>
> I don't think that the crossover cable is too long, GB. The maximum
> Ethernet cable length is 100m, and Psymaster's cable is only 20m long.
>
> However, it's quite possible that the crossover cable is sub-standard,
> especially if it's home-made. It might also be picking up
> electromagnetic interference from electrical wiring, appliances, etc.
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com

Psymaster
January 9th 04, 10:59 PM
"Steve Winograd [MVP]" > wrote on Sun, 14
Sep 2003 23:54:34 GMT in
microsoft.public.windowsxp.network_web:

> I don't think that the crossover cable is too long, GB.
> The maximum Ethernet cable length is 100m, and Psymaster's
> cable is only 20m long.
>
> However, it's quite possible that the crossover cable is
> sub-standard, especially if it's home-made. It might also
> be picking up electromagnetic interference from electrical
> wiring, appliances, etc.
>

It's not home-made, I bought it from a respected retailer.

Psymaster
January 9th 04, 10:59 PM
"GB" > wrote on Sun, 14 Sep 2003
23:43:43 GMT in microsoft.public.windowsxp.network_web:

> Hi,
>
> your cross over cable is too long, if you cannot affor a
> hub/switch, use a normal cat5 cable and a shorter
> cross-over (1m or 3ft) coupled to a female-to-female cat5
> adaptor.
>
> I am 99.9% confident this will cure your network ailments.
>

Are you really so sure? And what can I do now with my cable? I
forgot to mention that because 20 metres are not needed (the
computers need about 8-9 metres), the rest is coiled up. Could
that be a problem?

Steve Winograd [MVP]
January 9th 04, 10:59 PM
In article >, Psymaster
> wrote:
>"Steve Winograd [MVP]" > wrote on Sun, 14
>Sep 2003 23:54:34 GMT in
>microsoft.public.windowsxp.network_web:
>
>> I don't think that the crossover cable is too long, GB.
>> The maximum Ethernet cable length is 100m, and Psymaster's
>> cable is only 20m long.
>>
>> However, it's quite possible that the crossover cable is
>> sub-standard, especially if it's home-made. It might also
>> be picking up electromagnetic interference from electrical
>> wiring, appliances, etc.
>>
>
>It's not home-made, I bought it from a respected retailer.

It's possible that the cable is sub-standard, even though you bought
it from a respected retailer. It's possible that the cable has been
damaged by being coiled or bent too tightly or by other factors.

Configure both computers' network cards for 10 Mb, half duplex
operation, which puts the fewest demands on a cable. If it works with
those settings but not at 100 Mb or full duplex, the cable is
sub-standard or damaged.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Psymaster
January 9th 04, 10:59 PM
"Steve Winograd [MVP]" > wrote on Mon, 15 Sep
2003 06:32:11 GMT in microsoft.public.windowsxp.network_web:

> Configure both computers' network cards for 10 Mb, half duplex
> operation, which puts the fewest demands on a cable.

Hemmm, sorry if this sounds obvious, but how do I do that?

Steve Winograd [MVP]
January 9th 04, 11:00 PM
In article >, Psymaster
> wrote:
>"Steve Winograd [MVP]" > wrote on Mon, 15 Sep
>2003 06:32:11 GMT in microsoft.public.windowsxp.network_web:
>
>> Configure both computers' network cards for 10 Mb, half duplex
>> operation, which puts the fewest demands on a cable.
>
>Hemmm, sorry if this sounds obvious, but how do I do that?

See this web page:

Windows XP Network Troubleshooting - Problems with Network Cards
http://www.practicallynetworked.com/sharing/troubleshoot/networkcard.htm
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Psymaster
January 9th 04, 11:00 PM
"Steve Winograd [MVP]" > wrote on Mon, 15
Sep 2003 20:12:29 GMT in
microsoft.public.windowsxp.network_web:

> See this web page:
>
> Windows XP Network Troubleshooting - Problems with Network
> Cards
> http://www.practicallynetworked.com/sharing/troubleshoot/net
> workcard.htm
>

Thanks, I'll check it out and see what happens.

Psymaster
January 9th 04, 11:01 PM
Psymaster > wrote on Mon, 15 Sep 2003
22:56:17 GMT in microsoft.public.windowsxp.network_web:

>> See this web page:
>>
>> Windows XP Network Troubleshooting - Problems with Network
>> Cards
>> http://www.practicallynetworked.com/sharing/troubleshoot/net
>> workcard.htm
>>
>
> Thanks, I'll check it out and see what happens.
>

Nope, the same. Nothing got better.

Google