Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lotacus]

I've never had a problem with shared printing and everything works just as it should. And now with the new features of the usb port, I don't need to have, or turn on a computer just to print.

So far, using the utility to print with the printer hooked up to the dir655, everything still works like a charm. Now, I have not tried printing out large files, but standard documents print out fine without any delay that other people have been reporting. I'm using an HP 3100 series all in one printer.

A really nice feature as well that i've noticed is that I don't have to connect the printer using the utility as one would have to when sharing a usb drive. I just hit print in whatever program, and it prints automatically as if it where already connected. great stuff.

One thing I would like to see, if at all possible is that the utility will automatically release the printer once the print job is done so that other computers which may have jobs queued can automatically start the print job

[Alemaker]

Perhaps you can give a list of all your settings so the Dlink guys can reproduce the issue (use the .gws).

Settings are pretty much standard, out of the box stuff. Dir-655 Rev A2 with all defaults except named my own sid, use a pretty long TKIP/AES WPA2 only key, mixed g/n and channel width set to 20 because of an Intel 4965. Something is awry in the code if I can use 1.11 with no problems but not 1.20 and newer.
BTW, what program would you use to open a proprietary DLink gateway settings file (.gws)?

[EddieZ]

BTW, what program would you use to open a proprietary DLink gateway settings file (.gws)?

Haven't got a clue. But would like to find out...

[Lycan]

there is no program to open the file. It's to be loaded back to the router.

[Alemaker]

Lycan,

   Any ideas why some of us are seeing unacceptable lan printing performance with the newest code? Would love to use it but can't 

[EddieZ]

Lycan,

   Any ideas why some of us are seeing unacceptable lan printing performance with the newest code? Would love to use it but can't 

My name's not Lycan, but the issues seems very random. My two Vista stations don't suffer from it, tried with two brands of printers. The might achieve to replicate the issue in their lab, otherwise they might need more input on the configs or NIC's used?

[Sammydad1]

FYI....  LYCAN is our DLink provided Moderator and tie-in to their tech support team..... This forum would be useless without his intervention in-house !!!

SD1

[EddieZ]

Is he? Wow...

How stupid do you think I am? 

[Sammydad1]

simply because you responded to Alemaker's post to Lycan by saying you weren't Lycan....

whatever

[HazardX]

My thoughts:

Status->Statistics:
 menus seems somehow...misaligned (IE, labels aren't clearly related to any of the numbers floating around below them)

Tools->System Check:
It'd seem more logical to name that menu "ping test" since that what it calls itself when you select it. But that's probably just me...

Advanced->Port Forwarding (and other menus like it)
Seems to enjoy asking me if I want to save settings, even though I haven't even selected any particular box/changed anything at all. (the other menus with lots of input boxes/menus do the same...sometimes)

Advanced->Guest Zone
Menu isn't grayed out when wireless is completely disabled (it should be, because if wireless radio is off, how can I setup a guest zone?!) Though I'm sure that's not a priority, since most people probably bought the router FOR the wireless...not because it worked out to be the cheapest with a gigabit switch. :S

As far as actual functionality goes, DNS relay seems to work but the router *STILL* seems to confuse mdns broadcast clients in some way I haven't quite been able to track down. But ~mostly~ usable now, only when a client "fails" to get detected by the other mdns machines does it become problematic (in that it itself will be unable to resolve any *.local names for a few hours, and others can't see it, though sometimes other machines can resolve the troubled one's name, but not the other way around.

Its a little weird, and really hard to trigger the situation intentionally. BUT I can say that if I put my old DI-604 back in as my gateway, it works without a problem, so, either the DIR-655 is "right" and breaks stuff, or the DI-604 is broken and lets everything work when it shouldn't.


On a note related to the DI-604, its DHCP server (as screwed up as it was) would give the same address to my macs weather they were on wireless (I use a WRT54G for wireless not the 655 due to placement) or wired, this allowed them (somehow) to switch media types without interrupting any open connections, it was REALLY nice. But I'm sure that it was actually the DI-604's brokenness (or something in the verizon firmware).

[EddieZ]

My thoughts:

Status->Statistics:
 menus seems somehow...misaligned (IE, labels aren't clearly related to any of the numbers floating around below them)

Thta's an IE issue you have...not the router

Tools->System Check:
It'd seem more logical to name that menu "ping test" since that what it calls itself when you select it. But that's probably just me...

Semantics...

Advanced->Port Forwarding (and other menus like it)
Seems to enjoy asking me if I want to save settings, even though I haven't even selected any particular box/changed anything at all. (the other menus with lots of input boxes/menus do the same...sometimes)

Advanced->Guest Zone
Menu isn't grayed out when wireless is completely disabled (it should be, because if wireless radio is off, how can I setup a guest zone?!) Though I'm sure that's not a priority, since most people probably bought the router FOR the wireless...not because it worked out to be the cheapest with a gigabit switch. :S

Greyed out? It gives you the opportunity to configure while wireless is not yet active. Could be a useful situation. Most of the time the limitation of this is considered a nuisance...

As far as actual functionality goes, DNS relay seems to work but the router *STILL* seems to confuse mdns broadcast clients in some way I haven't quite been able to track down. But ~mostly~ usable now, only when a client "fails" to get detected by the other mdns machines does it become problematic (in that it itself will be unable to resolve any *.local names for a few hours, and others can't see it, though sometimes other machines can resolve the troubled one's name, but not the other way around.

Could you elaborate some more about this mdns issue? Trying to establish whether it is a DIR655- or 'just' your local Mac issue....

Its a little weird, and really hard to trigger the situation intentionally. BUT I can say that if I put my old DI-604 back in as my gateway, it works without a problem, so, either the DIR-655 is "right" and breaks stuff, or the DI-604 is broken and lets everything work when it shouldn't.

Try the new 1.21 beta...


On a note related to the DI-604, its DHCP server (as screwed up as it was) would give the same address to my macs weather they were on wireless (I use a WRT54G for wireless not the 655 due to placement) or wired, this allowed them (somehow) to switch media types without interrupting any open connections, it was REALLY nice. But I'm sure that it was actually the DI-604's brokenness (or something in the verizon firmware).
[/quote]

[HazardX]

Greyed out? It gives you the opportunity to configure while wireless is not yet active. Could be a useful situation. Most of the time the limitation of this is considered a nuisance...

'Cept the other wireless menus are grayed out, Guest zone being the only one that's not, so it seems like its more of an oversight, not a feature.

Try the new 1.21 beta...

Unless there's been a second beta release since I posted, I already am running the latest.

As far as the mdns goes, its not easy to predict the failures, or intentionally reproduce them, but a typcal solution (that seems SOMEWHAT reliable) is to pull the network cable from the mac with troubles, and reconnect it (this forces OSX to re-fresh its DNS caches, and rebroadcast all mdns stuff), then usually it works again. The same trick is less effective on the linux machines running avahi (usually they just get confused more).

I'm fairly confident it isn't the macs or linux machines configurations, since if I swap out the DIR-655 as the DHCP server/gateway for ANY other router I have (DI-604,BEFSR41,WRT54G), mdns works as it should.


There's two possibilities I can come up with based on the behavior of the failures (and what I've managed to put together about how mdns works). The first is that the DIR-655's handling of DNS requests is still not quite right, since it seems that mdns does DNS lookups on the name its trying to resolve before doing the multicast part (or looking in its multicast cache, I'm not sure which). But I suspect that sometimes the router just doesn't respond to the requests, and then OSX times out and everything breaks (I suspect it then poisons the mdns cache, since it caches that its a bad value, and since the machine doesn't re announce itself until mdns gets restarted, the computer doesn't rebroadcast for a significant amount of time). The other possibility is that the router is doing something horrible to multicast traffic, since mdns doesn't work AT ALL unless 'Enable Multicast Streams' is enabled. But I don't know enough about the internal functionality of avahi/apple mdns stuff to really tack down the source of the problem, And I haven't been able to find a tool to tell me where in the lookup process the failure occurred. I should also note, that the problems are only really bad with OSX 10.4/10.5, 10.3 seems to be somehow immune to the problems entirely (possibly because 10.3 has a much more primitive broadcast-oriented implementation of mdns but again, I can't really be sure).