Server 2003

[Guest]

I'm here in Houston recovering from Ike. Our Building was only without power for a week no power surges, no damages. When we brought our network backup we have a Minolta Dialta Di250 with a PI-3500 Print Controller. It was using dhcp and worked fine from the day i started working here(2 years) to the day we powered our network back up after the outage. It was using the same IP address as one of our file servers (grabbed the IP before the other machine booted), anyways the printer was deleted from the server it was shard from then when trying to readd it won't connect properly. all ports and everything verified. Company recently upgraded from server 2000 to server 2003 any ideas? same issue on a Konica 7030(had other issues those were resolved). Also whenever i try to add a preshared printer to a computer that existed on the network previously it gives me "Windows cannot connect to the printer. Make sure that you have typed the name correctly, and that the printer is connected to the network." but if i add it \\server\printername it works fine. it shows up in active directory but gives the previous error when trying to add. if added manually prints fine.

Positive this is a network issue.

[RSFarrer]

a few notes, a server should normally have an IP in a range that is outside the DHCP scope. you may have to delete the DHCP lease for the copier and then turn it off/on to grab a new IP.
also check the DNS on Server 2003 as it is heart of network communication and you can manually delete the copier entries and/or manually add the copier back later if you need to.

Personally, I normally put the printers at static IPs so that I can browse, maintain, etc at IPs that I know. For large fleets, DHCP is better, but for only 2 MFPs/copiers, 2 static IPs outside the DHCP scope iw what I do.

Hopefully you are using the Server 2003 as the in-house DNS source. Then it will quicken the network response.
To test or as a workaround, if the Server hosting the printers is a static IP, then use \\IPaddress\printername to add the network printer.

OR go to Start, Run and type \\IPaddress [of the server] and hit enter
you should see the printer and server shares in the window that pops up. Double-Click on the printer you want and it should add.

Best wishes

[skeptik]

both are setup on static IP's and dns is in hoouse the server is out of the scope. i can print to them as an internet printer only. It may be some active directory group policy's interfering? i dont know so much about the network side of things on this. It appears to me that the printer is there and prints and is configured properly.

the Di250 says test page failed would you like to run troubleshooter at the end of the local printer setup with port IP_172.2.17.xxx(should i be using the di250 driver or the pi3500 print controller driver? i tried both with negative results)(also, same bad results when trying to install as internet printer)

The konica installs fine, to local tcp/ip port IP_172.2.17.xxx but everything just hangs in the print que. and dont print, unless as mentioned before it is added an an internet printer

My only other concern outside of bad active directory policy's, is their firewall. not sure if this would affect it, don't know about how it works, cept that it is a proxy based sidewinder g2

[RSFarrer]

another idea. I use the Standard TCP/IP port printing every day and normally use the raw setting which uses port 9100.

perhaps switch to LPR in the properties and see if that helps. sometimes you can use PRINT or PORT1 for the queue name or try blank.

I have 3 cousins in your area still digging out after IKE...hope all is going better.

[skeptik]

by default this printer is set to port 10000, do i need to change this on the hardware as well as the printer settings on the server?

I'm on the west side of town, theres alot of wind damage and still alot of power out (2 weeks after) but my work nor home received any major damages.

[RSFarrer]

I forgot about those port settings...we used that a long time ago. we used to set one to 10000 and the other to 10001.

I don't know if that one will accept a lpr setting then. sorry, not much more to think right now.