We are a christian school, we have a variety of VMware servers, HP procurve network switches, and HP radio ports in place. We have a variety of printers. Some of which are HP laserjet 1320's. The 1320s in pariticular keep going offline or freezing. WHen they do this we can see it happening through HP WEB Jetadmin. They need to be rebooted and then they work fine.
All PC's are using WIN XP professional. Why do the printers keep doing this??
An expert who has achieved level 2 by getting 100 points
An expert that got 5 achievements.
An expert whose answer got voted for 20 times.
An expert who has answered 20 questions.
Re: Going off line or freezing
There have been many issues with formatters on both those machines, such as usb not working right out of the box,
1. flash the firmware for the machine.
2. if that doesn't fix the problem then replace the formatter board.
3. also use the pcl5 or 5e drivers, they tend to be more reliable than the pcl6 drivers.
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I'm going to assume you can get in the command line interface. Go into the command mode (type "config t" with out the quotes ) then type "ip http server" press enter, type exit to get out of command mode and then "write memory" to save your configuration. Remember, vlan 1 on the switch MUST have a IP address for you to be able to access the web interface.
I'd contact HP ProCurve support at 1-866-my-procurve. They will ask for the show tech all report from the system to help diagnose the problem. It sounds like there's a significant problem with this switch to cause this problem. I've dealt with ProCurve switches for going on 9 years and haven't seen this problem.
What do you need it configured to support? Multiple subnets? VoIP support? Here's an example to support 2 subnets, VLAN 1 Data and VLAN 2 Voice. This switch is the VLAN router for the site and it is also the default gateway for all the devices on the network.
; J4899A Configuration Editor; Created on release #H.10.50
hostname "HP 2650 dot 11 layer 3" snmp-server contact "Your contact info here" snmp-server location "Server Rack - Upper Switch" time timezone -5 time daylight-time-rule Continental-US-and-Canada interface 49 name "Uplink to HP2650 port 49 - 192.168.105.12" flow-control exit interface 50 name "Uplink to HP2650 port 49 - 192.168.105.13" flow-control exit ip routing timesync sntp snmp-server community "public" Unrestricted vlan 1 name "Data" untagged 1-46 ip address 192.168.105.11 255.255.255.0 ip helper-address 10.50.3.2 tagged 49-50 no untagged 47-48 exit vlan 2 name "Voice" untagged 47-48 ip address 10.50.3.11 255.255.255.0 ip helper-address 10.50.3.2 tagged 1-46,49-50 exit ip route 0.0.0.0 0.0.0.0 192.168.105.1 spanning-tree Always turn on Spanning Tree spanning-tree priority 0 This switch is the master Spanning Tree operator. password manager password operator
qos dscp-map 101110 priority 6
snmp-server community "public" Unrestricted
vlan 1 name "Data_Vlan" untagged 1-28 ip address 188.8.131.52 255.255.255.0 exit vlan 2 name "Voice_Vlan" ip address 10.9.180.5 255.255.255.0 qos dscp 101110 tagged 1-28 voice exit
Program the port that the PBX is in as a untagged port on Vlan 2
First, be sure to assign an ip address(in the proper subnet) to each VLAN.
Second, use the ip helper-address command in the context of each VLAN, the address used should be the address of the DHCP server
Third, Add a scope for each additional VLAN on the DHCP server.
The switch will route the DHCP request to the proper server based on the ip helper-address command parameter and based on the ip address of the VLAN that is passed tot he server, a DHCP address in the proper subnet is automatically configured.
The Procurve 1800 SWITCH series supports 802.1p, 802.1q VLANS, 802.3ad LACP, 802.3x Flow control, RFC1534 DHCP/BOOTP interoperation, the Cisco 2800 series is a ROUTER and dependant on its IOS version will support a multitude of routing/security features that the Procurve just isnt designed to do.
There is nothing special about these switches other than that they are managed. Managed means they have some means of connecting to them and "managing" them like you do when you configure a wireless router by going to some ip address in your browser to access the configuration. They usually are able to communicate statistics, set up virtual subnetworks, monitor ports, mirror ports, control which ports can access which others, set speed limits on ports, etc... A normal switch is "dumb", there is nothing to configure and it just does it's thing, connecting anybody and everybody that are connected to any of it's ports. Procurve switches are popular because they are great switches, there are other managed ones that can be had for much less, I use 48 port managed Linksys that have/exceed these capabilities for way cheaper... examples
You'll need to obtain a comms lead - connects into the console port of the switch then into an RS232 port on your laptop. Then, you will be able to connect using hyper terminal and you can give the switch an IP address, username, etc. Even a hard-reset won't allow you to configure an IP address as by default it needs to be configured through the lead. Will they not talk without being configured? If you just hard reset them, they should just behave as unmanaged switches.
These are non-manageable switches, not configurable thus no IP. You should be able to plug it in to your home wiring, however, if you don?t have a server or dhcp server you will have to assign IP addresses to your computers and other network devices manually.