Please help me share my printer on this network~ thx

Hey all,

I'm about to try to figure out how to do this, but in the mean time I wondered if any of you had a better (easier) solution.

The DGL4300 portion of the network resides in my house. PC#1 is my g/f's laptop, and it's set up to be able to print to the print server wirelessly. The DI624 and other pcs are in my garage, and I'd like to be able to print to the print server from that portion of the network.

I can barely connect to the DGL4300 wirelessly from the garage due to distance and structural interference, and it's a pain to have to switch to that network every time I want to print something. Additionally I'd like to be able to share files between the two networks (PC#4 is set up as a server of sorts).

Can anyone here offer any advice on the matter? I can provide additional details if you need them

Thanks!

And connect the network cable to a local port on the DI-624 and NOT the Internet Port.

Grumpy

Hmm. I like the simplicity of this idea, but I kind of want to keep the two networks separate. If I can't find a way to do that then this way will work. Thanks.

Also, I'll check the documentation of the 624 as what port to connect the incoming cable for the AP feature.

Hmm. Ok, I've played with this setup for the better part of 4 hours and have come to these conclusions (PC#2 is the main testbed for this):

1) I can use routing so that I can see the DGL4300 from PC#2, behind the DI624. Woot!
2) I can ping the print server from PC#2. Woot!
3) I cannot access any shares from PC#2 and PC#1. Meh.
4) I cannot print to the print server from PC#2.
5) It's very easy to lock up the DGL4300, needing a manufacturer's reset, by entering a setting it doesn't like in the routing table. (Took me one try before I got smart and backed up the router settings-doh!)

So upon thinking about it, there's really no reason why I even need the DI624 to be a router at all--like Ice said, make it an access point and be done with it.

I'm doing that next. Thanks for the replies, guys.

Are you sure? I haven't set up a DI-624 as an AP, but the routers I have set up as APs still want the connection to the router to be made from the WAN port (according to their documentation - and they have worked as documented).

Yes, I am. For all computers to be able to access each other, they need to be in the same IP address range (ie. 192.168.1.X) since they are private NON-ROUTABLE IP addresses. The DI-624 should have an IP Address in the same range as the DGL4300 also.

GrumpyI agree with your last two sentences. What I was questioning was whether that would be violated once the router is made into an AP. I haven't spent any time peeking and probing into the internal secrets of these little boxes, but the ones I have set up to be APs say in their documentation to connect the WAN port to the router. Everything does remain in the same local LAN. So, the router-now-AP must be smart enough internally to know the WAN port is now no longer a "WAN."

The user does need to check the documentation, though, since what you say "should" be correct if the router makes no change to how it treats the WAN port when in the AP mode.

Your computers should receive an IP address from the DHCP server in your DGL4300. You shouldn't have to set them manually.