Permabanned
- Joined
- 28 Nov 2003
- Posts
- 10,695
- Location
- Shropshire
I have just bought a cheap used HP LaserJet netowrk printer, but stupidly I didn't check if I had a spare port on my Netgear DG834 ADSL router. I am now having to swap cables with another printer.
I may want to add network points in other rooms and in my workshop next time we re decorate, so with thought to future proofing would this allow me to connect up to 23 ports off the router?
http://www.ebay.co.uk/itm/HP-ProCur...puting_NetworkSwitches_RL&hash=item45fd528689
There are lots of variants of HP ProCurves on Ebay, all about the same price, and I am unsure what features I need. I may want to add another 2 or 3 PC's or laptops to the network, and be able to plug them in wherever suits, plus be able to use the printers from any PC.
I have seen this HP one listed, but from the HP site FAQ's I don't know if this 1/2 duplex thing is an issue, I know nothing about networking I'm afraid :
Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support full-duplex? The hub ports can only operate in half-duplex mode. If the attached device is running in full-duplex mode, and cannot auto-negotiate to half duplex, it will cause a lot of late collisions on the network, degrading performance for all nodes.
Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support 802.1Q/802.1p? The HP ProCurve 10/100 Hubs allow 1522 byte size packets tagged with an 802.1Q tag but do not decode the VLAN ID. The hubs do not participate in VLAN tagging or VLAN priorities. The packets will be forwarded without any problems.
The hub, switch, or router will correctly sense (not auto-negotiate) the 10Mbps or 100Mbps speed. Since the end node was configured for a specific speed and duplex state, and therefore does not negotiate, the hub, switch, or router will choose the communication mode specified by the 802.3u standard, namely half-duplex. With one device running at half-duplex and the device on the other end of the connection at full-duplex, the connection will work reasonably well at low levels of traffic. At high levels of traffic the full-duplex device (end node, in this case) will experience an abnormally high level of CRC or alignment errors. The end users usually describe this situation as, "Performance seems to be approximately 1Mbps!". Often, end nodes will drop connections to their servers. In this same situation, the half-duplex device will experience an abnormally high level of late collisions. The network administrator must take care to verify the configuration of each network device during installation. Also, check the operational mode of each network device. That is, check both how you configured it and also that it comes up as you expect, for example, at 10Mbps/half-duplex.
Thanks for any advice.
I may want to add network points in other rooms and in my workshop next time we re decorate, so with thought to future proofing would this allow me to connect up to 23 ports off the router?
http://www.ebay.co.uk/itm/HP-ProCur...puting_NetworkSwitches_RL&hash=item45fd528689
There are lots of variants of HP ProCurves on Ebay, all about the same price, and I am unsure what features I need. I may want to add another 2 or 3 PC's or laptops to the network, and be able to plug them in wherever suits, plus be able to use the printers from any PC.
I have seen this HP one listed, but from the HP site FAQ's I don't know if this 1/2 duplex thing is an issue, I know nothing about networking I'm afraid :
Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support full-duplex? The hub ports can only operate in half-duplex mode. If the attached device is running in full-duplex mode, and cannot auto-negotiate to half duplex, it will cause a lot of late collisions on the network, degrading performance for all nodes.
Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support 802.1Q/802.1p? The HP ProCurve 10/100 Hubs allow 1522 byte size packets tagged with an 802.1Q tag but do not decode the VLAN ID. The hubs do not participate in VLAN tagging or VLAN priorities. The packets will be forwarded without any problems.
The hub, switch, or router will correctly sense (not auto-negotiate) the 10Mbps or 100Mbps speed. Since the end node was configured for a specific speed and duplex state, and therefore does not negotiate, the hub, switch, or router will choose the communication mode specified by the 802.3u standard, namely half-duplex. With one device running at half-duplex and the device on the other end of the connection at full-duplex, the connection will work reasonably well at low levels of traffic. At high levels of traffic the full-duplex device (end node, in this case) will experience an abnormally high level of CRC or alignment errors. The end users usually describe this situation as, "Performance seems to be approximately 1Mbps!". Often, end nodes will drop connections to their servers. In this same situation, the half-duplex device will experience an abnormally high level of late collisions. The network administrator must take care to verify the configuration of each network device during installation. Also, check the operational mode of each network device. That is, check both how you configured it and also that it comes up as you expect, for example, at 10Mbps/half-duplex.
Thanks for any advice.