Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
My setup:
Dell laptop with Windows xp sp2
--I use Windows Firewall and it is shut off
Macbook with 10
Canon mp610 scanner/printer
DNS-323 NAS (firmware: 1.04)
Dlink dir-655 gigabitrouter
I am able to log in to the server just fine
I can see and edit and whatever to all my shared folders on the dns-323
I can see the printer (labeled as 'lp') when browsing to the dns-323 over my network using a windows window
I can right-click on this printer and choose 'connect', following all instructions and install the printer drivers
After the printer is installed, I choose 'properties' and then 'Print Test Page'. I get a pop-up which says:
"Test page failed to print. Would you like to view the troubleshooter for assistance? Test page failed to print."
Next step
On the advice from many forums, including this one I try to create a local port.
I choose "add printer"
then "Local printer attached to this computer"
choose "create a new port" type of port "Local port"
little popup comes up "Enter a port name"
I have tried every possible combination in the world and I keep getting the same message:
"The network name cannot be found"
I have tried to connect with the mac as well. Some type of issues, can do whatever with the files, but absolutely cannot get the printer to work.
I also have the latest version of Pure Networks Network Magic - that doesn't see the printer. Not sure if that matters.
I am completely stumped. Any detailed advice out there someone can help me with?
much thanks,
Scott
Last edited by scottnath (2008-03-29 01:17:57)
Offline
First step - with the printer connected to the DNS-323, go to the status page, does it show you the printer as connected - if you don't see it, I don't think you'll get the printer shared.
Second step - install the printer directly connected to the computer as per the manufacturer's instructions, make sure it works.
Now - select the printer, open printer properties, select the ports tab, click add port, select local port and click new port, in the port name dialogue enter //<ip-address-of-DNS-323>/lp and then click ok.
If you're getting a "the network name cannot be found" message, make sure you have NetBIOS over tcp/ip enabled AND the DNS-323 and the computer are in the same workgroup.
Offline
1)
status page says:
PRINTER INFO :
Manufacturer: Canon
Product: MP610 series
2)
done. works great (been installed and functioning fine for months)
3)
Yup, both in same workgroup
went to :
Network Connections>>Local Area Connection>>properties>>general tab>>Internet Protocol (TCP/IP)>>properties>>Advanced>>WINS tab>>checked Enable NetBios over tcp/ip.
no change.
Offline
I was playing around with mine a few days back and everything stopped working as well. I did get it up and running again, though.
What I had to do was remove all mappings to the drive(s), removed the printers, shut the dns down, then reboot my pc. Once I did that and re-setup the mounts and printers, everything was fine...
Not sure why, but just removing the printer, and leaving the mounts, then rebooting, didn't work.
Hope this helps.
Offline
I've used the method I outlined above on both XP Pro & Vista Business without problems, but after folks reported the "network name can not be found " message I started poking around and discovered I could reproduce it by disabling NetBIOS over tcp/ip.
Another thing I noticed is the text of the message changes to "Network path was not found" if you change the port name, so it is finding the named device.
I suspect it can also be used with a standard tcp/ip port so I'll take a look at that over the weekend.
Offline
Thanks Terry,
I tried the full reboot of both. Same problems exists.
Fordem,
thank you for looking into this. really appreciate it.
Offline
scott
Do you have fun_plug installed?
Before trying to create the local port - use telnet to create the /.lpd folder and set the permissions to 777
mkdir /mnt/HD_a2/.lpd
chmod 777 /mnt/HD_a2/.lpd
In previous testing I had no problem creating the local port, possibly because I had not reformatted my disks after upgrading to fw 1.04, but I have since switched disks and setup a RAID1 array, and all attempts to get the print server functional this weekend failed, including creating the local port (I got the same network name can not be found message) until I manually created the folder.
Once I had done that I was able to create the local port as described above and print with no further difficulty.
Offline
The 1.04 firmware puts my .lpd directory a different partition now. It's in /mnt/HD_a4.
Offline
blahsome wrote:
The 1.04 firmware puts my .lpd directory a different partition now. It's in /mnt/HD_a4.
Well - I looked in my /mnt/HD_a4 - and sure enough there was .lpd - but I couldn't get the print server functional until I manually created it in /mnt/HD_a2, and that includes following the instructions in the D-Link support site FAQ.
I still can't get it to print using those instructions, but it prints just fine using the "local port" instructions provided above, after I manually created the folder.
Offline
In general, I've found "add-on" print servers on these network devices (e.g. routers, NAS enclosures, etc) to be fragile at best. Stars have to align in a certain way before they function properly. My print server function works, but the DNS-323 absolutely refuses to spin down when a printer is connected, despite trying numerous workarounds.
I've concluded that it's generally better to leave each hi-tech gadget to perform its respective core function. Based on that principle, my DNS-323 right now is a NAS box and nothing more.
I don't want to telnet in and delete .lpd every full moon. In the meantime, I'm picking up an Ethernet laser printer for $100.
Offline
A correction to my earlier post - it DOES print if I follow the instructions from the FAQ - but when I check the ports tab in properties there is no port selected - since the Windows test page lists the port name as \\<DNSname>\lp this might be similar to the "local port" setup.
I also observed a noticeable delay in updates to the printer status page, even though there was no corresponding delay in the actual printing - a Windows test page completes printing before the status page shows it was sent, and the status page will show the job as printed for perhaps a minute or two after it has completed.
blahsome - I tend to agree with you, but I have found the low end networked printers to be just as finicky
Offline
Hi
After downloading 1.04 and reformatting my hard drives I'm now unable to print using the USB print server. The status pages show the make and model of my usb printer (standard printer not multifunction). One difference I noticed was that 1.03 firmware had a .lpr and 1.04 has lp as the shared printer. From the above messages it looks like the dlink firmware is very buggy and possibly broken and the printing does not work. Does anyone have any idea on how to fix it without hacking the box. I'm currently not using the fun pack as it will void my warranty (after asking dlink). So it looks like this one may need to be packed up and taken back for a refund if no one can help me. PS: Dlink support is hopeless.
Thank you
Offline
I had it all setup on my system with 1.03 I reformatted my disks when I went to 1.04 and lost printing.
I tried deleteing and re-adding: no go
I tried adding the local port: no go
Then I tried fordem's mkdir and chmod on HD_a2 and everything worked fine as before on all my computers.
Thanks fordem's
Offline
So I forgot to mention when I started this post that I only had one drive in my DNS-323, and thus that drive was formatted as 'standard'.
I didn't try any of the hacks, but tried everything else to no avail.
Yesterday, I added a second drive, reformatted both for RAID 1, and now the printer works following the simple DLink FAQ instructions:
http://support.dlink.com/faq/view.asp?p … =dns%2D323
The only other change is that I used the supplied DNS-323 disk utility which mounted the Volume_1 drive as local drive F:. I don't think that should have made a difference though.
Sadly, this didn't fix the MacBook yet. Can still see/edit files with that mac, but the printer isn't receiving the print jobs. Will keep trying.
Offline
Glad I could help - I must point out however, that the mkdir etc. was a suggestion from someone else in this forum, I don't remember whom, and the local port trick also came from someone else, but I think that one might have been a different forum and a different print server - other folks share their knowledge and I'm just passing it on.
Offline
Pages: 1