Topic 'Re: [AB] V1000H: unable to print to LAN printer' in forum 'Telus' - dslreports.com

Re: [AB] V1000H: unable to print to LAN printer

Thu, 11 Oct 2012 21:25:09 EDT

rustydusty posted : Can't install/run a DC without DNS installed. By then, may as well do exchange at the same time :D

Re: [AB] V1000H: unable to print to LAN printer

Thu, 11 Oct 2012 00:59:44 EDT

ruiner posted : There are quite a few home printers that are found by broadcast now so their IP doesn't even matter. Recommending static's to most of the users on here would be like recommending that they run a domain controller. Completely overkill.

Re: [AB] V1000H: unable to print to LAN printer

Tue, 09 Oct 2012 23:37:52 EDT

rustydusty posted : Regardless, static will ALWAYS be more reliable than a reserved. If you want reliability of no issues, I always go static. Reservations have their uses, and to devices that are always connected and never move, static always. There's a reason DHCP's have scopes/ranges. Printers and servers always go static. Only reason I've ever used a reservation for a standard client is a specific program that needs port forwarding on that specific machine isn't in just one place and can't have a static assigned.

I'm done, proven my point. There's tons of guides showing by anything printers, server or network equipment is static assigned. Do your reservations if you want, but you will have issues with it at one point and you will understand why, then.

Adios!

Re: [AB] V1000H: unable to print to LAN printer

Tue, 09 Oct 2012 19:35:42 EDT

ruiner posted : Let's see, there are how many IT people seeking advice for their department here? There are small home NAS devices that are very easy to move. And a lot of routers with this feature called, "save configuration."

Yes that wouldn't work all of the time moving to a different model but most people would have maybe 2 or 3 devices that would warrant having a reservation anyhow. You would have to redo all of your forwards and some other settings in that case so you would be better off having a screenshot or printout if you can't remember it easily.

And then there are some devices like the Actiontec that supposedly sometimes have issues forwarding a port to a device it didn't hand an IP out to. I haven't had a problem using a Linux DHCP server but apparently some people have.

I'm sorry DHCP pissed on your cornflakes years ago but for 99.99% of the users on here static makes zero sense.

Re: [AB] V1000H: unable to print to LAN printer

Tue, 09 Oct 2012 18:47:50 EDT

rustydusty posted : Who moves a NAS? You move a device that has static, you shouldn't be doing IT. I wouldn't move our 12TB Iomega unless it was the entire network moving with it. If you are switching routers, ensure it's on the same range or move all the devices to the new range. Really simple. Wait until you have your DHCP device crap out, you'll see why then. Routers go all the time, and having things static is a lot simpler when you replace that piece of hardware. Ensure it's on the same range and it's done, instead of setting up reservations for devices again.

Re: [AB] V1000H: unable to print to LAN printer

Tue, 09 Oct 2012 17:39:40 EDT

ruiner posted : So because you had issues once or twice you think all of the average users here should deal with the hassle of using static IPs?

What if I want to take my printer or NAS to my buddies place whose router is on a different subnet or has that IP in use, not to mention DNS servers. Having to reenter information is more of a headache than having to copy and paste a MAC address if something dies or gets replaced. That is if you don't bring the abortion of a firmware on the Actiontec into the equation.

And typically port forwarding is easier with a DHCP reservation since you can have a list of devices and addresses that gets updated automatically.

Re: [AB] V1000H: unable to print to LAN printer

Mon, 08 Oct 2012 22:52:26 EDT

rustydusty posted : There is use for them, but for anything printing, server related I always just assign a static and forget it. Makes port forwarding even easier and then there's 0% chance that the IP could change. Just seen reservations fail a couple times, and I would rather not even put it in the chance of having issues. Even if I loose my DC at home which does all DHCP and requests, all servers still continue one, even if client side is buggered till I get it fixed. Static's there is just no chance of issues, except hardware failure which you can't predict, even with proper UPS backup in place, or just fault hardware.

Re: [AB] V1000H: unable to print to LAN printer

Mon, 08 Oct 2012 20:19:28 EDT

titan_rw posted :

said by rustydusty:

You never want to do DHCP reservations, anyways. Why they have them is beyond me. A DHCP server can and eventually will crap out, where as a static there is 0% possibility of issues, except hardware failures.

For devices like printers, routers, switches, then yes, I agree, DHCP reservations are a bad idea. Hard code the IP in the device.

For user devices (PC's, laptop's, phones, etc), I use DHCP reservations all the time. You could assign them static ip's, but then when you take your computer to another network you have to change your ip settings. Leaving it on dhcp assigned, but having a reserved ip at home gives you a 'fixed' ip at home, and will still work when not at home.

One could just leave it on dhcp all the time, but some programs work better when the ip's on the network don't change. QOS settings are typically done by ip. Port forwarding also needs ip's that don't change. DHCP reservations allow things like port forwarding to work, and still allow flexibility when connecting to other networks.

No, they're not required, but there is definitely a use for them.

Re: [AB] V1000H: unable to print to LAN printer

Mon, 08 Oct 2012 17:33:22 EDT

anon posted : @rulner: that's what I ended up doing; there were a couple of quirks - after connecting the server to the DI-624, I had to hard-reset it to get a connection to the router, then do "add route server-ip router-ip", ignore the "no such device" error message that gave me, and then telnet in and set a static IP _within_ the V1000H's range, disconnect from the D-624, connect to the V1000H, and do another hard-reset. Then it was just a matter of editing the IP in the printer properties on my Linux boxes, and deleting and reinstalling the printer on my wife's Windows systems ( the latter wouldn't accept just editing the IP address ). Once that was done, everything was working. Thanks for the help and advice.

Re: [AB] V1000H: unable to print to LAN printer

Mon, 08 Oct 2012 14:11:20 EDT

ruiner posted : Yeah with enough printers that would take a little bit more coordination. But you're spouting off about "nightmares" which the only way that would happen is if a big chunk of printers were replaced at the same time. That's just poor planning if it wasn't staged. And not only that but recommending that advice to a forum with SOHO users at most is ridiculous. How many home users have enough devices to warrant a network map? KISS.

@Al: You're going to need to plug the print server and another PC into the DI-624. Then the print server can get an IP from the DI and you telnet in and set a static IP. After that it should work on the Actiontec. The DI doesn't need to be hooked into your home network for this.

Re: [AB] V1000H: unable to print to LAN printer

Mon, 08 Oct 2012 07:07:00 EDT

anon posted : I haven't been able to get into any settings on the print server box. It's supposed to be possible to telnet in IF there's a route between it and the computer - but of course, adding a route requires knowing the server's IP address ....
As far as I've been able to discover, the print server doesn't have a web interface.

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 20:53:35 EDT

rustydusty posted : Why I said static doesn't need to be changed on anything, where as a MAC needs to be whenever a controller or board is replaced. Any copier can have the IP entered while standing infront of the machine. Print a config page off, replace the board and pop same IP in. No need to even contact the print server operator. Such a pain dealing with changing MAC's and doing DHCP Reservations, unless you have nothing but time on your hands. Less intervention for the print server operator when copier repairs are done. You can tell the tech to input the same IP and the admin doesn't even need to login into server. Are you even a NA or SA or just an 'expert' on home based routers?

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 19:40:06 EDT

ruiner posted : Oh its so difficult to change a MAC address, and a much larger hassle than entering an IP through a crappy copier interface.

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 19:31:59 EDT

rustydusty posted : That was not the person's fault, however if everything was static and documentation was in place, it would of been a lot easier to re-do the print server. They were also doing the reservations by MAC, which can change when a controller board is replaced on the machine. Nothing but a huge hassle, where as if it's static, you pop the same IP into the copier once the board is replaced and nothing on print server needs to be touched. It's just a huge time saver WHEN things go bad.

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 19:28:43 EDT

ruiner posted : There are people that don't know what they are doing in companies of all sizes.

What happened? Their DHCP server crashed and they didn't have the configuration backed up? Yeah that's really a huge flaw in DHCP. What happens if you lose your network diagram? Why should I waste a bunch of time running a scanner when its not necessary?

Say our DNS servers change. Now I have to update them on thousands of machines when DHCP could push it out automatically. Even if you push a script they still have to be restarted to get it. DHCP will update when the lease expires.

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 19:14:08 EDT

rustydusty posted : There's hundres of network scanners you can download if you don't have a proper network diagram in place. May take 2-3 minutes to run . Talk to Flint, a giant oilfield company about printers being on DHCP reservations. They will tell you the horror story, and why they now do static's. Is that large enough scale for you? Probably not, that was only a 3k of printers.

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 19:06:22 EDT

ruiner posted : If its beyond you then don't comment on it. Any server can crap out so why bother with anything?

With a static there is an exponential increase in the chance of a conflict with each new address you add. Good luck finding it when the conflict doesn't occur until hours or days after you have assigned the IP.

Do you think its better to manage a large list of IP's on a piece of paper? There is this thing called a backup that is used when a server craps out.

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 19:00:19 EDT

rustydusty posted : You never want to do DHCP reservations, anyways. Why they have them is beyond me. A DHCP server can and eventually will crap out, where as a static there is 0% possibility of issues, except hardware failures.

Re: [AB] V1000H: unable to print to LAN printer

Sun, 07 Oct 2012 15:57:03 EDT

ruiner posted : What you are talking about is a DHCP reservation not a static IP. You need to get into the print server's settings and manually enter an IP that is outside of the Actiontec DHCP range.

If the print server only has a web interface then you'll need to hook it back into the DI-624 how you were using it before so you can log in and set the static IP.

Re: [AB] V1000H: unable to print to LAN printer

Fri, 05 Oct 2012 21:19:35 EDT

anon posted : before the new router arrived, I had it set up with a static IP on the DI-624, and tried to do the same with the Actiontec by assigning a static IP to the server's MAC address - which didn't work. It seems that the Actiontec is not seeing the device's MAC address. But I'll give it another try in case something wasn't right the first time.

Re: [AB] V1000H: unable to print to LAN printer

Fri, 05 Oct 2012 20:51:56 EDT

anon posted : When I say print server, I mean a box into which I plug a printer and which connects to the router or switch with an ethernet cable.

Re: [AB] V1000H: unable to print to LAN printer

Fri, 05 Oct 2012 16:16:53 EDT

ruiner posted :

said by alpreston :

I'm going to try using the DI-624 in place of the switch, to see if that helps.

The switch on the DI-624 won't make it work if a different switch didn't help.

It sounds like you need to either set up a static IP in the PRINTER SETTINGS, or a second DHCP server using a different IP range.

The DI-624 would be able to act as a secondary DHCP server but setting a static IP is probably less work. You would need to make sure the DI-624's LAN address is in the Actiontec's subnet (probably 192.168.1.xxx) and change the range of the addresses it gives out. By default the Actiontec should be assigning 192.168.1.64 to 192.168.1.253 so you want it to be below that range.

If that doesn't work, the printer's ethernet port may have gone bad with very coincidental timing.

Re: [AB] V1000H: unable to print to LAN printer

Fri, 05 Oct 2012 15:26:30 EDT

rustydusty posted : When you say print server, are you talking fiery or Server 2008 R2 with Print Management installed and simply holding drivers and possibly spooling the documents?

Re: [AB] V1000H: unable to print to LAN printer

Fri, 05 Oct 2012 07:15:59 EDT

anon posted : I've tried different ports. I had a switch between the print server and the router to start with - that was the way I had it set up with the DI-624. The Actiontec saw the switch, but not the print server, I couldn't even ping the server. I'm going to try using the DI-624 in place of the switch, to see if that helps.

Re: [AB] V1000H: unable to print to LAN printer

Fri, 05 Oct 2012 01:07:06 EDT

rustydusty posted : Always setup printers on static. A big company found out wrong way that DHCP reservations on thousands of printers isn't a good idea. They ended up wasting a ton of time having to re do every printer with a static.

Re: [AB] V1000H: unable to print to LAN printer

Thu, 04 Oct 2012 22:41:16 EDT

ruiner posted : You could also have a bad port on the Actiontec. Have you tried another port?

Placing a switch between the printer and Actiontec could fix it if its a handshaking issue. If you don't have a switch you can use, just disable DHCP on the DI-624 and hook a cable from the Actiontec to the D-Link, and another from the D-Link to the printer. Both should be in the D-Link's LAN ports.

Otherwise I would check if you can set the printer to a static IP in the printer's settings. Use an IP outside of the Actiontec's DHCP range so it doesn't get assigned to another device using DHCP.

Re: [AB] V1000H: unable to print to LAN printer

Thu, 04 Oct 2012 12:47:13 EDT

anon posted : We have both ADSL and TV on the system. The old setup was a Telus-supplied modem, which I think was a Speedtouch, to which I'd connected my own DI-624 router. I can't check the name or model, as the tech took it back when he hooked up the V1000H.

I suspect the V1000H router is not responding to the print server's DHCP query, or not recognizing/accepting it's MAC address: though it sees there is a connection, detects the connection speed, and reports a number of packets sent and received, it's not assigning an IP address to the device.

Re: [AB] V1000H: unable to print to LAN printer

Thu, 04 Oct 2012 11:27:02 EDT

nss_tech posted :

said by alpreston :

The server was previously connected to a Dlink DI-624 router, not a modem.

I guessed as much but what modem did you have?

The Actiontec is... not perfect and is likely the cause of you problems. Are you on ADSL only or do you have TV also?

Re: [AB] V1000H: unable to print to LAN printer

Thu, 04 Oct 2012 10:38:07 EDT

WackyGaru posted : The V100H is a router as well.

Re: [AB] V1000H: unable to print to LAN printer

Thu, 04 Oct 2012 07:21:37 EDT

anon posted : The server was previously connected to a Dlink DI-624 router, not a modem.

Re: [AB] V1000H: unable to print to LAN printer

Thu, 04 Oct 2012 07:21:31 EDT

anon posted : Yes - the print server's connection speed shows up (in yellow - the other connected devices are shown in green), but no entry shows up in the connected devices list - only the set top boxes and computer(s).

I've tried using different cables with no change. Today I hooked up the server through my old router and made sure it wasn't assigned a static URL. After rebooting it, it showed up in the DI-624's DHCP dynamic connection list, so I know that part works. I then reconnected it to the V1000H and rebooted it, but got the same indications as before.

Re: [AB] V1000H: unable to print to LAN printer

Wed, 03 Oct 2012 15:15:12 EDT

ruiner posted : You're saying that its showing up on the section that shows the port status but not under the IP listing at the bottom?

First thing I would try is using a different ethernet cable.

Re: [AB] V1000H: unable to print to LAN printer

Wed, 03 Oct 2012 04:18:52 EDT

nss_tech posted : What modem did you have before the Actiontec?

Re: [AB] V1000H: unable to print to LAN printer

Wed, 03 Oct 2012 02:47:31 EDT

anon posted : I removed the DHCP reservation and rebooted the print server, but no change in results. LAN status still shows the connection speed in yellow, and the server is not showing up in the list of connected devices.

Re: [AB] V1000H: unable to print to LAN printer

Tue, 02 Oct 2012 22:21:20 EDT

spock posted : I'm sure you have already done this but check to see that the printer is not assigned a static IP and reboot the printer.

[AB] V1000H: unable to print to LAN printer

Tue, 02 Oct 2012 03:00:19 EDT

anon posted : During Optik-TV set up, the tech replaced my older modem and router with an Actiontech V1000H. Most things are working fine, but we are unable to use a network printer connected to one of the LAN ports. It looks from the LAN status that the router is seeing a connection, but it isn't detecting the print server's MAC address or assigning it a URL I tried setting up DHCP reservation, manually entering the server's MAC address and assigning it a URL, but that didn't help.
I should add that on the LAN status page, the device's connection speed is shown in yellow rather than green like the other connections. There's nothing else in the instructions or on Actiontech's website about configuring the LAN connections, so I'm stymied as to what to do.