Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

Running a dedicated NIC for an hp printer with network conne

by Nov 30, 2012 1:17AM PST

Hi, we have several old laser jets that have either a LPT or network card connection. Our network has a domain controller. We only have one RJ-45 wall jack by each workstation. So the route I would rather take is as mentioned. Install another NIC, change the ip on the adapter to a different sub-net then put the printer on the same subnet and print from that NIC. Any suggestions on a ip for each and configuring this to work? Thank you

Discussion is locked

akersrus has chosen the best answer to their question. View answer
8 Posts
- Collapse + Expand Details

Best Answer

- Collapse -
Sure. Why not?
by Forum moderator Nov 30, 2012 1:23AM PST

I would never do that because setup can overtax most IT staffers. Instead I'll install a switched hub to get more ports and avoid configuration and support issues.

But if you want to use a dedicated NIC and can configure this then it is possible for it to work. But again, not a setup I'd use at the office.
Bob

- Collapse -
Thanks
by akersrus Nov 30, 2012 2:34AM PST

I have used separate or dedicated switches in this instance,what I learned was switches don't go bad often, but when they do it can be really taxing ( good descriptive) to trace it if you have more than one switch on a network. My idea is to keep it separate from the rest of the network. But I know it is not ideal nor is it something that is attempted often. That is what I am asking for a little help in configuring it.

- Collapse -
Such help is rare.
by r. proffitt Forum moderator Nov 30, 2012 2:41AM PST

Because it's so specific to the LAN, the OSes involved, the drivers, and tinkering with the print spooler this is something your IT staffer must accomplish on their own since they will have to support it.

I won't do this in our office because I don't allow high wire acts. That is, we want a LAN without a need to tinker or tweak. It must work.

As to your comment about troubleshooting the LAN, I've never found that to be taxing. But maybe it's because we have spare hubs and cables. I've run into sad situations where they don't have any spares and the boss is berating the IT staff for not being able to spot the bad part without swapping.
Bob

- Collapse -
I understand
by akersrus Nov 30, 2012 2:49AM PST

We are one of those companies that does not have a budget for spares, and I have been on the berating end of that situation. I am thinking the first thing I would have to have is a crossover cable. Would you agree with that?

- Collapse -
Maybe.
by r. proffitt Forum moderator Nov 30, 2012 2:51AM PST

The last NIC I installed (actually the last dozen) had AUTO MDX so I could use either straight or crossover cables.

Is your IT staff unaware of MDX and the move to AUTO MDX?
Bob

- Collapse -
Yes, unaware
by akersrus Nov 30, 2012 2:58AM PST

Most of our NIC are inexpensive 10/100/1000 cards or on board chipsets. I am limited in current schooling of modern network adapters. I used to setup two PC's with this type of direct cable connection.

- Collapse -
Onboard chipsets are now getting this auto mdx.
by r. proffitt Forum moderator Nov 30, 2012 3:03AM PST

Always check the specs. It's nice since I am down to just a pair of crossover cables in the IT room. And both are not in use. Just there if we need them.
Bob

- Collapse -
(NT) Thanks for your help
by akersrus Nov 30, 2012 3:11AM PST
Back to Networking & Wireless forum

CNET Forums

Operating Systems
Software
Electronics & Gadgets
Hardware
Tablets & Mobile Devices
General Help
Brand Forums
Roadshow Autos
Off Topic

Other Forums

Forum Info