Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 499
  • Last Modified:

Wireless LAN veeerry slow, even PING takes ages

I am setting up a wireless connection between my Win2K desktop and my WinXP notebook. The desktop is connected to internet via a DSL modem on an internal ethenet card. This works fine. For the WLAN it has a wireless USB adapter. The notebook has a built-in wireless adapter. I am setting up a peer-to-peer connection between the desktop and the notebook.

Both computers can see eachother, after a while, but the connection is extremely slow. Although on both computers signal strength and quality is "high" and "excellent", even pinging is very slow. 1-2 out of 4 ping attempts time out, successful attempts have an average response time of about 500 ms or more.

For the moment I don't have any encryption or security enabled (until things speed up).

Any suggestions?
0
cadenza
Asked:
cadenza
3 Solutions
 
grbladesCommented:
Hi cadenza,
You could try changing the channel incase there is interferance on the one you are on.
0
 
virtuoso1Commented:
Are they in the same workgroup?  All critical updates and service packs applied?  

In xp, open an explorer window, goto tools, folder options, view tab.  Scroll down, and turn off--Use simple file sharing.  Try mapping a drive directly--open my network connections, tools > map network drive, pick a drive letter and then below type the path to where you want the share to connect to, like \\Xpbox\share.

Also goto start > run, \\compwanttoconnecto\c$ which is the hidden admin share, and when it prompts you, type in the user name and password, and check the box to remeber the password.
0
 
pseudocyberCommented:
I'm seconding grblades idea - interference on the channel.
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
natcomCommented:
also the note book is SP2 ?
0
 
cadenzaAuthor Commented:
hi

first: thanks for all your comments!

then the answers to your questions/suggestions:
- I tried several channels, to no avail
- workgroups are the same, XP: SP2, 2K: SP4
- I share a directory on the notebook
- I could not find the "use simple file sharing" option

In the mean time I re-did and checked all network settings (ip, SSID etc.). The result is:
- I can ping the desktop from the notebook, with response times varying from 1 ms to 1500 ms, but more often 1-7 ms now than before
- I can not ping the notebook from the desktop
- on the notebook doing start > run > \\desktop\c$ result in a new browser window showing the C: root directory of the desktop, but only after 1 minute or so. I can browse directories, but each step takes like 1 minute. Opening a 33 kB .pdf file takes another minute at least [for "desktop" I fill in the IP address, not the name]
on the desktop doing start > run > \\notebook\c$ results in an error message after a minute or so: "the network cannnot be found"
- in the Explorer on the desktop I see under \Network\Entire Network\Microsoft Windows Network\MyWorkgroup both computers and under the notebook branch I see the directory I shared

So: the speed still is very low. And: in the desktop Explorer I can see the notebook after some time, but not with start > run etc. But in the notebook Explorer I can not see the desktop, but start > run etc gives access to the full harddisk of the desktop.

Hmm... I feel we're getting further, but I don't understand what is going on

By the way: the desktop has Symantec Internet Security, of which I configured the firewall to trust my notebook.
0
 
cadenzaAuthor Commented:
and:

on the desktop I can ping 127.0.0.1, but not 192.168.1.1 (the ip address of the desktop's wireless USB adapter)
0
 
ahaji2002Commented:
Hello,
Can you provide me:
 1. the network configuration of the desktop and the laptop
     (start >> run >> command, and type "ipconfig /all")
 2. the route information of both desktop and laptop
     (still at the same DOS prompt, type "route print")


antonius aji
www.openesc.com
0
 
cadenzaAuthor Commented:
DEsKTOP:

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : cadenza-1
Primary DNS Suffix  . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : (ZD1211)IEEE 802.11b+g USB Adapter #2
Physical Address. . . . . . . . . : 00-0E-2E-3F-44-9C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.1.1

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-18-D8-C5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : dinsdag 9 november 2004 7:53:32
Lease Expires . . . . . . . . . . : vrijdag 12 november 2004 7:53:32

===============================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0e 2e 3f 44 9c ...... ZyDAS ZD1211 802.11b+g Wireless LAN
0x1000004 ...00 0b 6a 18 d8 c5 ...... SiS NIC SISNIC
===============================================================
===============================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.1.254    192.168.1.33        1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1        1
      192.168.1.0    255.255.255.0      192.168.1.1     192.168.1.1        1
      192.168.1.0    255.255.255.0     192.168.1.33    192.168.1.33        1
      192.168.1.1  255.255.255.255        127.0.0.1       127.0.0.1        1
     192.168.1.33  255.255.255.255        127.0.0.1       127.0.0.1        1
    192.168.1.255  255.255.255.255      192.168.1.1     192.168.1.1        1
    192.168.1.255  255.255.255.255     192.168.1.33    192.168.1.33        1
        224.0.0.0        224.0.0.0      192.168.1.1     192.168.1.1        1
        224.0.0.0        224.0.0.0     192.168.1.33    192.168.1.33        1
  255.255.255.255  255.255.255.255      192.168.1.1     192.168.1.1        1
Default Gateway:     192.168.1.254
===============================================================
Persistent Routes:
  None


NOTEBOOK:
Windows IP Configuration
Host Name . . . . . . . . . . . . : Compaq
Primary Dns Suffix  . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-0F-B0-0F-03-53

Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Broadcom 802.11b
Physical Address. . . . . . . . . : 00-90-4B-97-38-72
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.1.1

===============================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f b0 0f 03 53 ...... Realtek RTL8139 Family PCI Fast Ethernet NIC - Packet Scheduler Miniport
0x3 ...00 90 4b 97 38 72 ...... Broadcom 802.11b - Packet Scheduler Miniport
===============================================================
===============================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.2        30
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1        1
      192.168.1.0    255.255.255.0      192.168.1.2     192.168.1.2        30
      192.168.1.2  255.255.255.255        127.0.0.1       127.0.0.1        30
    192.168.1.255  255.255.255.255      192.168.1.2     192.168.1.2        30
        224.0.0.0        240.0.0.0      192.168.1.2     192.168.1.2        30
  255.255.255.255  255.255.255.255      192.168.1.2               2        1
  255.255.255.255  255.255.255.255      192.168.1.2     192.168.1.2        1
Default Gateway:       192.168.1.1
===============================================================
Persistent Routes:
  None
0
 
ahaji2002Commented:

Can you try to use networking bridging .. i.e. you bridge the Wireless NIC and LAN NIC - (see here: http://www.wown.com/j_helmig/wxpbrdge.htm) , unfortunately I have no Windows 2000. In XP Pro, it is very easy to do: select the two NIC, and right click and select bridge.

Or you can try to have ICS (Internet Connection Sharing) on Wireless NIC, it means that while the LAN NIC got IP assignment from DSL Modem (LAN NIC as DHCP client), the Wireless NIC will be the the device for DHCP server (activated by ICS) - which in turns give IP assignment for your notebook. Windows will assign the NIC with ICS with IP: 192.168.0.1, so your notebook IP (DHCP enabled) will have 192.168.0.x

Oh ya .. before doing that, make sure that you have most current driver for Wireless NIC at the desktop (once I got a problem due to old driver which XP never complained before)

rgds,
a.aji
www.openesc.com
0
 
cadenzaAuthor Commented:
Won2K does not have bridging. According to some sites I found on onternet it can be done if you add a suitable driver for it, but haven't done that yet.
But: I think your 2 suggestions aim at making internet available for the notebook. I may want this in the future, but I think for the moment it would be better to get the simple peer to peer network connection up and running. Now browsing the desktop's c: drive from the notebook over the network takes 1 minute to e.g. step one directory level deeper. I have had a cable network before, and on that one you could browse much, much faster. I don' see why this would not be possible with a wireless network.
0
 
cadenzaAuthor Commented:
hi all,

for a while I have been too busy to see if I could get any further with this. Now I changed the location of the notebook with respect to the dekstop, tried again and guess what? It works!! Still not perfect, but now at least I have something to build on.
I split the points between the contributions that I feel helped me.

Thanks to all for your energy!
Wim
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now