D-Link DI-524

  • Thread starter Thread starter Dave Bachmann
  • Start date Start date
D

Dave Bachmann

I'm having a bit of grief moving from a Belkin F5D6231-4 to the D-Link. The
Belkin has worked fine for a couple of years but I wanted to move up to G. I
have a heterogeneous network (Linux and WinXP, laptops and desktops, wired &
wireless) and everyone can access the net via the D-Link but can not see
each other via ping, "My network places" or SAMBA. When I switch back to the
Belkin everyone can get to the net and see each other just fine.

I've been thru all the settings, but nothing that I've changed seems to
work. I've got to assume there are quite a few folk out there sharing PCs
with a D-Link, so if someone who's doing it successfully can give me a hint
or two, 'twould be most gratefully appreciated.

Dave
 
What is the DLink connected to? From your description of the problem, I
have a hunch that you may be chaining routers in some fashion and that
possibly DHCP was turned off in the Belkin and is enabled in the DLink, but
you don't give much information to work with.
 
Outbound, the D-Link is connected to a Motorola SurfBoard and thence to
cable. Inbound it has wired connections to 2 PCs running Ubuntu 5.10, 1
running XP Home, and 1 running XP Pro. On the wireless side it has another
PC running XP Pro a laptop running XP Pro, and another laptop running XP
Home. The identical configuration is used with the Belkin. No firewalls are
running on the individual PCs.

The Belkin has the "Use as an access point" feature disabled and acts as a
DHCP server.

Any suggestions will be most gratefully received.

--
Invert name and ISP in order to respond
GTS said:
What is the DLink connected to? From your description of the problem, I
have a hunch that you may be chaining routers in some fashion and that
possibly DHCP was turned off in the Belkin and is enabled in the DLink,
but you don't give much information to work with.
--
Click to expand...
 
That's very odd. If you run ipconfig /all on the two XP machines, do they
show the same subnet? Better yet, perhaps you could post the output here.
--

Dave Bachmann said:
Outbound, the D-Link is connected to a Motorola SurfBoard and thence to
cable. Inbound it has wired connections to 2 PCs running Ubuntu 5.10, 1
running XP Home, and 1 running XP Pro. On the wireless side it has another
PC running XP Pro a laptop running XP Pro, and another laptop running XP
Home. The identical configuration is used with the Belkin. No firewalls
are running on the individual PCs.

The Belkin has the "Use as an access point" feature disabled and acts as a
DHCP server.

Any suggestions will be most gratefully received.
Click to expand...
 
The subnet's the same. I'm attaching sanitized copies of ipconfigs for 2 of
the XP PCs with each connected to the Belkin and then to the DLink. Is there
anything that catches your eye?

Windows IP Configuration PC#1/Belkin



Host Name . . . . . . . . . . . . : PC#1

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : HomeNetWork



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : HomeNetWork

Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Controller

Physical Address. . . . . . . . . : 00-0C-3C-E3-67-76

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.2.72

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::20c:76ff:fe3c:e367%4

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.1

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : Wednesday, December 28, 2005 16:12:28 PM

Lease Expires . . . . . . . . . . : Monday, January 18, 2038 19:14:07 PM

=============================================================

Windows IP Configuration - PC#1/D-Link



Host Name . . . . . . . . . . . . : PC#1


Primary Dns Suffix . . . . . . . :


Node Type . . . . . . . . . . . . : Unknown


IP Routing Enabled. . . . . . . . : No


WINS Proxy Enabled. . . . . . . . : No


DNS Suffix Search List. . . . . . : myisp.net






Ethernet adapter Local Area Connection:






Connection-specific DNS Suffix . : myisp.net


Description . . . . . . . . . . . : NVIDIA nForce MCP Networking
Controller


Physical Address. . . . . . . . . : 00-0C-3C-E3-67-76


Dhcp Enabled. . . . . . . . . . . : Yes


Autoconfiguration Enabled . . . . : Yes


IP Address. . . . . . . . . . . . : 192.168.0.100


Subnet Mask . . . . . . . . . . . : 255.255.255.0


IP Address. . . . . . . . . . . . : fe80::20c:76ff:fe3c:e367%4


Default Gateway . . . . . . . . . : 192.168.0.1


DHCP Server . . . . . . . . . . . : 192.168.0.1


DNS Servers . . . . . . . . . . . : 192.168.0.1


fec0:0:0:ffff::1%1


fec0:0:0:ffff::2%1


fec0:0:0:ffff::3%1


Lease Obtained. . . . . . . . . . : Wednesday, December 28, 2005
15:47:13 PM


Lease Expires . . . . . . . . . . : Wednesday, January 04, 2006
15:47:13 PM


=============================================================

Windows IP Configuration - PC#2/Belkin



Host Name . . . . . . . . . . . . : PC#2-0010


Primary Dns Suffix . . . . . . . : office.uvic.ca


Node Type . . . . . . . . . . . . : Unknown


IP Routing Enabled. . . . . . . . : No


WINS Proxy Enabled. . . . . . . . : No


DNS Suffix Search List. . . . . . : office.uvic.ca


HomeNetWork


uvic.ca






Ethernet adapter Local Area Connection:






Connection-specific DNS Suffix . : HomeNetWork


Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E
Gigabit Ethernet Controller


Physical Address. . . . . . . . . : 00-0E-CC-28-7B-6D


Dhcp Enabled. . . . . . . . . . . : Yes


Autoconfiguration Enabled . . . . : Yes


IP Address. . . . . . . . . . . . : 192.168.2.96


Subnet Mask . . . . . . . . . . . : 255.255.255.0


Default Gateway . . . . . . . . . : 192.168.2.1


DHCP Server . . . . . . . . . . . : 192.168.2.1


DNS Servers . . . . . . . . . . . : 192.168.2.1


Lease Obtained. . . . . . . . . . : December 28, 2005 16:14:36


Lease Expires . . . . . . . . . . : January 18, 2038 19:14:07


=============================================================

Windows IP Configuration - PC#2/D-Link


Host Name . . . . . . . . . . . . : PC#2-0010


Primary Dns Suffix . . . . . . . : office.uvic.ca


Node Type . . . . . . . . . . . . : Unknown


IP Routing Enabled. . . . . . . . : No


WINS Proxy Enabled. . . . . . . . : No


DNS Suffix Search List. . . . . . : office.uvic.ca


myisp.net


uvic.ca






Ethernet adapter Local Area Connection:






Connection-specific DNS Suffix . : myisp.net


Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E
Gigabit Ethernet Controller


Physical Address. . . . . . . . . : 00-0E-CC-28-7B-6D


Dhcp Enabled. . . . . . . . . . . : Yes


Autoconfiguration Enabled . . . . : Yes


IP Address. . . . . . . . . . . . : 192.168.0.101


Subnet Mask . . . . . . . . . . . : 255.255.255.0


Default Gateway . . . . . . . . . : 192.168.0.1


DHCP Server . . . . . . . . . . . : 192.168.0.1


DNS Servers . . . . . . . . . . . : 192.168.0.1


Lease Obtained. . . . . . . . . . : December 28, 2005 15:59:22


Lease Expires . . . . . . . . . . : January 4, 2006 15:59:22
 
Sorry to say I'm baffled. I compared the ipconfigs side by side and see
nothing that sheds any light on the problem. I like the DI-524 and have
installed quite a few for clients without ever seeing a problem like this.
I'm starting to wonder if the unit could be defective, though it seems
unlikely it would fail this way on the LAN side while otherwise working.
Any chance you could test it on another network? When you try to ping
between machines does it just time out?
 
I don't have another set of machines to try it on, but I have run into
something new. Testing things before I used a couple of XP Pro machines and
the pings would time out in either direction. Testing the DLink again today
I found that I could both ping and see files on a Pro machine from an XP
Home, but not the other way around! Needless to say, things work
bidirectionally as they should with the Belkin. I don't have anything
special configured in either hosts file. I'm starting to wonder now if this
could somehow be an OS issue? Another possibility is that there is something
"contaminated" in the Pro machine that's "uncontaminated" in the Home
machine. In either case, tho, I'm not too sure where to start looking, but
given that I can do things properly in 1 direction, I don't think it's a
defective unit.
 
Back
Top