• February 26, 2025, 12:58:39 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Can connect via wireless  (Read 7188 times)

blanka

  • Level 1 Member
  • *
  • Posts: 3
Can connect via wireless
« on: December 12, 2010, 03:33:10 PM »
Hi,

I have  a weird issue (I think?). I can connect via LAN but not via wireless (Win 7 and Win XP).

I am using a DIR-655 as my router.

Here is the weird thing; when I ping the device from wireless , 192.168.0.32, I get destination host unreachable. When I ping the device with the name, I get the response, but it appears to be from my ISP.  Copy of the ip config (Win 7 maching) and ping are below. Any suggestions?

H:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : OPI-LT02
   Primary Dns Suffix  . . . . . . . : OPISYSTEMSINC.COM
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : OPISYSTEMSINC.COM
                                       langdon1.efirehose.net

Wireless LAN adapter Wireless Network Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
   Physical Address. . . . . . . . . : 00-21-6A-A7-E9-89
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 70-1A-04-9D-3B-E4
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-26-B9-1C-5D-C5
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : langdon1.efirehose.net
   Description . . . . . . . . . . . : Intel(R) WiFi Link 5300 AGN
   Physical Address. . . . . . . . . : 00-21-6A-A7-E9-88
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::cc83:bf83:26bc:b4cc%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.130(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : December-12-10 10:07:39 AM
   Lease Expires . . . . . . . . . . : January-18-47 10:54:05 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 184557930
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-11-91-2A-00-26-B9-1C-5D-C5

   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{A5C1B0DF-1558-4586-A1E8-B840A1627FED}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1036:3050:3f57:ff7d(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::1036:3050:3f57:ff7d%28(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{BC6AA9DA-439F-4CBA-AF2E-093364754E6A}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{38C8413B-39F1-491B-B16C-52B488CDC4AB}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.langdon1.efirehose.net:

   Connection-specific DNS Suffix  . : langdon1.efirehose.net
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.130%32(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Disabled


Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

H:\>ping 192.168.0.32

Pinging 192.168.0.32 with 32 bytes of data:
Reply from 192.168.0.130: Destination host unreachable.
Reply from 192.168.0.130: Destination host unreachable.
Reply from 192.168.0.130: Destination host unreachable.
Reply from 192.168.0.130: Destination host unreachable.

Ping statistics for 192.168.0.32:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

H:\>


H:\>ping d-link-323-1

Pinging efirehose.net [72.13.167.34] with 32 bytes of data:
Reply from 72.13.167.34: bytes=32 time=19ms TTL=61
Reply from 72.13.167.34: bytes=32 time=31ms TTL=61
Reply from 72.13.167.34: bytes=32 time=7ms TTL=61
Reply from 72.13.167.34: bytes=32 time=25ms TTL=61

Ping statistics for 72.13.167.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 31ms, Average = 20ms

H:\>



Logged

Wiggs

  • Level 3 Member
  • ***
  • Posts: 137
    • dwithers.com
Re: Can connect via wireless
« Reply #1 on: December 13, 2010, 05:41:09 AM »
Quote from: blanka on December 12, 2010, 03:33:10 PM

H:\>ping 192.168.0.32

Pinging 192.168.0.32 with 32 bytes of data:
Reply from 192.168.0.130: Destination host unreachable.
Reply from 192.168.0.130: Destination host unreachable.
Reply from 192.168.0.130: Destination host unreachable.
Reply from 192.168.0.130: Destination host unreachable.
It seems odd that the "Destination host unreachable." is not coming from 192.168.0.1 which is you gateway (router).  Can you ping 192.168.0.1?
192.168.0.130 is your local IP address. 

The pinging of the d-link name which returns 72.xxx.xxx.xxx is also not correct. 

Regards,

Wiggs
Logged
Wiggs,

DNS-323, 2-500GB Seagate Drives, FW 1.08
D-Link DGS-1005G Gigabit Switch
Asus O!Play Air Media Player
WinXP PC
OpenSuse 11.2 PC
Macbook 5,2 - Snow Leopard

blanka

  • Level 1 Member
  • *
  • Posts: 3
Re: Can't connect via wireless
« Reply #2 on: December 13, 2010, 10:08:57 AM »
Hi Wiggs,

Thanks for the reply. I have no problem pinging the router (D-Link DIR-655);

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

H:\>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 8ms, Average = 2ms

H:\>

The 72.XX.... IP is provided by my ISP (obviously) but I don't understand why the ping returns that address connected via wireless. I have tried this machine (Win 7 wireless) and two Win XP netbooks via wireless, same result. None of the wireless machines get a response when I ping the local IP.

When I ping from a LAN computer that does work with the DNS-323, if i ping the IP, I get the response from the IP (192.168.0.32). If I ping the name, I get the same response as above (from IP 72.xx.....).

Very strange, suggestions?

Logged

jamieburchell

  • Level 6 Member
  • *
  • Posts: 947
Re: Can connect via wireless
« Reply #3 on: December 13, 2010, 02:43:29 PM »
Could you provide an ipconfig report from one of the LAN connected machines that works?
I can only assume there is a difference in configuration between wireless and LAN clients, or your router is set to do something odd.
Logged
If your little 323 is not working right,
You've racked your brains and been up all night
Take a deep breath and wipe away the sweat,
Login as web admin and try a factory reset!

blanka

  • Level 1 Member
  • *
  • Posts: 3
Re: Can connect via wireless
« Reply #4 on: December 14, 2010, 10:31:06 AM »
Hi Jamie,

Thanks for the reply. I am out of town this week until Thursday. I will post the results then.
Logged

HSishi

  • Level 2 Member
  • **
  • Posts: 73
Re: Can connect via wireless
« Reply #5 on: December 14, 2010, 01:27:55 PM »
Can you ping *any* LAN device from WLAN or vice versa? If not, my guess is the router separates WLAN from LAN and no devices can see any other in the other network type.

So every ping into the other network type goes via internet and then the router should block all pings (firewall functionality).

//HSishi
Logged