Not unsupportable but close enough, I'd post in general work chat but I don't think it would get a lot of exposure with the geeks (like me) on the forum.
I was going to refresh two computers in a retail store - one of which was over 6 1/2 years old (wow - how did it miss the last refresh?).
I had both new PCs in the office yesterday and threw the OS and a "loadset" (basically a set of applications that are commonly used with certain positions - this one is for a sales computer in a retail store). No errors pop up during the entire process. They completed early this morning so they were ready to be delivered.
I get to the store and plug in the first one, all the local peripherals install flawlessly (receipt printer, scanner etc.). Then, I try to install the network printer that is in the back. Hmm, PC won't see it. Odd. I try a few more times and no dice. I confirm that I have the right IP address for the printer plus I send test pages from the computer I was using for the tickets - no issues there.
OK, maybe it is a network printing issue? I map to some on the floor and they map fine - I can even send test pages. Odd
I try a few more times - no dice. I can't even ping the printer from that computer but I can from others.
OK, time to move to the other PC - I'll also know if it is the loadset, OS version or the model. Nope, this one is perfect, all printers install and I can send test pages to them all, including the one in the back room.
Hmm...
Just for poops and giggles, ipconfig /release and ipconfig /flushdns and ipconfig /renew. Nope, still not working. Check the mapping, I can ping the other IP locations in the store - even the IPs that are being used next to it (one below and two up - one up isn't being used). Hmm..
Disconnect the VoIP phone and still won't see the printer. I even trace the cable back to the LAN and move it to a different port on the router. Still won't see it.
Hmmm.....
DNS lists check out fine, full network connectivity, I can browse the web etc..
I call a friend and he remotes in. He checks the map of the printer and tries to ping the printer name - oddly, when he did a tracert it did pick up the right IP address but could not trace to it nor could he ping it.
He checks NSconfig (I think that's it) and it sees the IP address but won't connect to the printer. He can see the printer from his computer (over 200 miles away) and can ping it from his PC.
We double check IP, DNS, networking, and all is good, this damn thing won't even connect to the printer.
We spent over 2 hours on this issue and to save time (yeah, too late) we decided it was best to just re-reload the OS and loadset, hopefully that'll fix it but due to the slower connections in the store I won't know until sometime late tomorrow or early Friday.
I was going to refresh two computers in a retail store - one of which was over 6 1/2 years old (wow - how did it miss the last refresh?).
I had both new PCs in the office yesterday and threw the OS and a "loadset" (basically a set of applications that are commonly used with certain positions - this one is for a sales computer in a retail store). No errors pop up during the entire process. They completed early this morning so they were ready to be delivered.
I get to the store and plug in the first one, all the local peripherals install flawlessly (receipt printer, scanner etc.). Then, I try to install the network printer that is in the back. Hmm, PC won't see it. Odd. I try a few more times and no dice. I confirm that I have the right IP address for the printer plus I send test pages from the computer I was using for the tickets - no issues there.
OK, maybe it is a network printing issue? I map to some on the floor and they map fine - I can even send test pages. Odd
I try a few more times - no dice. I can't even ping the printer from that computer but I can from others.
OK, time to move to the other PC - I'll also know if it is the loadset, OS version or the model. Nope, this one is perfect, all printers install and I can send test pages to them all, including the one in the back room.
Hmm...
Just for poops and giggles, ipconfig /release and ipconfig /flushdns and ipconfig /renew. Nope, still not working. Check the mapping, I can ping the other IP locations in the store - even the IPs that are being used next to it (one below and two up - one up isn't being used). Hmm..
Disconnect the VoIP phone and still won't see the printer. I even trace the cable back to the LAN and move it to a different port on the router. Still won't see it.
Hmmm.....
DNS lists check out fine, full network connectivity, I can browse the web etc..
I call a friend and he remotes in. He checks the map of the printer and tries to ping the printer name - oddly, when he did a tracert it did pick up the right IP address but could not trace to it nor could he ping it.
He checks NSconfig (I think that's it) and it sees the IP address but won't connect to the printer. He can see the printer from his computer (over 200 miles away) and can ping it from his PC.
We double check IP, DNS, networking, and all is good, this damn thing won't even connect to the printer.
We spent over 2 hours on this issue and to save time (yeah, too late) we decided it was best to just re-reload the OS and loadset, hopefully that'll fix it but due to the slower connections in the store I won't know until sometime late tomorrow or early Friday.
Comment