![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Protocols and Routing IP, IPX and other protocol support |
![]() |
|
|
Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Mar 2008
Posts: 1
OS: Windows XP Pro (SP2)
|
Slow transfer times between XP/Linux direct connection
Hi,
I've a problem with network routing which is beginning to drive me crazy! I basically have two PCs, one which is running Windows XP Pro, and another which is running Ubuntu 7.10. Both have USB wireless adapters connected to them, plus a crossover ethernet cable attached to their ethernet network interfaces linking the two machines together. My end result is to have any traffic between these two machines travel over the ethernet interfaces, but any other network traffic to travel over the wireless interfaces. To simplify things for the time being, I have downed both of the wireless interfaces and am concentrating solely on the ethernet connection (192.168.0.20 (Windows) and 192.168.0.21 (Linux)). I have Samba installed upon the linux box to export a directory which is then mapped within XP to a particular driver letter. Unfortunately, copying any files from the linux box over to the Windows box takes absolutely ages - for example a 52MB directory is taking roughly 150 seconds to transfer! I have attempted to setup the networking routes for this connection but from that very slow transfer time I'm guessing that I've done something wrong. If someone could take a look at the details below and point out any obvious problems, or if they have any suggestions as to something else that could be causing the delay, then that would be very helpful. Thanks, Neil Code:
C:\Documents and Settings\Neil> ipconfig
Windows IP Configuration
Ethernet adapter Ethernet (to Duffman):
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
C:\Documents and Settings\Neil>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10004 ...00 17 31 b2 7e 04 ...... Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 192.168.0.20 192.168.0.20 30
192.168.0.20 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.0.21 255.255.255.255 192.168.0.20 192.168.0.20 1
192.168.0.255 255.255.255.255 192.168.0.20 192.168.0.20 10
224.0.0.0 240.0.0.0 192.168.0.20 192.168.0.20 10
255.255.255.255 255.255.255.255 192.168.0.20 192.168.0.20 1
===========================================================================
Persistent Routes:
None
C:\Documents and Settings\Neil>ping 192.168.0.21
Pinging 192.168.0.21 with 32 bytes of data:
Reply from 192.168.0.21: bytes=32 time<1ms TTL=64
Reply from 192.168.0.21: bytes=32 time<1ms TTL=64
Reply from 192.168.0.21: bytes=32 time<1ms TTL=64
Reply from 192.168.0.21: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\Neil>
Code:
neilf@duffman:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:63:DE:10:5B
inet addr:192.168.0.21 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::240:63ff:fede:105b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4244 errors:0 dropped:0 overruns:0 frame:0
TX packets:10628 errors:0 dropped:0 overruns:0 carrier:0
collisions:2754 txqueuelen:1000
RX bytes:557211 (544.1 KB) TX bytes:11634433 (11.0 MB)
Interrupt:10 Base address:0xe800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6233 errors:0 dropped:0 overruns:0 frame:0
TX packets:6233 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13661007 (13.0 MB) TX bytes:13661007 (13.0 MB)
neilf@duffman:~$ netstat -nr
Kernel IP routeing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.20 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
neilf@duffman:~$ ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20) 56(84) bytes of data.
64 bytes from 192.168.0.20: icmp_seq=1 ttl=128 time=0.197 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=128 time=0.234 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=128 time=0.271 ms
64 bytes from 192.168.0.20: icmp_seq=4 ttl=128 time=0.319 ms
--- 192.168.0.20 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.197/0.255/0.319/0.046 ms
|
|
|
|
![]() |
| Thread Tools | |
|
|