Connect to printer via ip address windows xp

It is used to identify your printer among other devices on the network so that computers can communicate with it. Finding your printer's IP address is simple and takes only a few moments. For Windows XP, find the printer for which you want to locate the IP address and right click it, then select "Properties" and then "Ports. Widen the first column to display the IP address.

Leeann Teagno has been writing professionally since Wish you all the best! Thank you very much for this good old tip!

We had to change mainboard on old XP machine, which is the programming controller for laser cutting machine, and after repair the above mentioned symptoms showed up. Actually worked!!! This is one of the best help articles for XP to 10 printing there is, worked like a champ, even with having to use a net use LPT1 command for an old DOS program. Thanks for posting!! Please help what to do.

A working solution to a problem which ought not to exist! Just one point which could have been mentioned. I assume the server ip4 address should be static and not dynamically allocated, otherwise addresses may be reallocated differently by the router? Unfortunately, not all routers provide this option and it may be necessary to amend the ip address from time to time on the XP machine.

Is there a work-around for this! I actually have a solution to the issue.. I created a user called printer with administrator rights and remote desktop user in user management on the windows 10 machine making sure the printer is shared.

I went to the security tab on the printers properties and added the printer user account and gave it full permission. I then gave the pc a static ip address. So example of the printer i was working with in question.

I also installed SMb1 complete on both xp and windows 10 machines. I also dsiabled windows 10 credentials in network connection sharing center.. Notify me of followup comments via e-mail. You can also subscribe without commenting. Leave this field empty. Home About. The credentials supplied are not sufficient to access this printer. We cannot think of anything on the network that has changed, and no settings on the printers have changed.

I'm trying to understand what it could mean that I cannot connect to them via IE until they have been reset. Possible problem here could be increased traffic on the network and the use of a hub instead of a switch although this is unlikely if multiple users are streaming any sort of data; in a hub network you're going to have data hitting data, which causes more data to hit data, and in a larger network things could lock up.

Although in modern networks this should hopefully be unlikely but it is occasionally still implemented. Now with that said lets take a look at layer 1 of the OSI model, have you checked the physical cabling? Switching out a faulty cable could be the fix, way to simple to work right? But it does at times work. Now I'll say lets check layer 2. Is there any STP configured on your switches? Could this be causing you to have routing loops? Data goes somewhere but goes nowhere.

Simply just look at the lights on the switch, how rapid are the flashing? How often are they flashing? Its possible you could have a network storm going on, once again data goes somewhere but never goes anywhere. Finally have you used Wireshark by chance to see the network traffic? Brief overview on Wireshark if you haven't used it you can see where everything is going, see where things are getting lost, how much data is being used, what protocols are being used, what websites people are viewing, who is in your network, who should be and shouldn't be in your network.

Do these have internal NIC cards or are they connected to an external print server? If they are all the same model with all of the same NICs try a firmware update. Has any of the switching infrastructure chnaged?

Universal Print Driver? If not then are your drivers properly updated? Have you tried resetting the print spooler instead of rebooting? The only thing I can think of is that there is an IP address conflict on the network. This would explain why you can ping the address, but not get the page to load in IE, because the IP address has been assigned to another device or computer.

Perhaps someone installed a router on the network to use as a switch and is handing out IP addresses?