Network printer not working after Win 7 upgrade

I have a Kodak ESP 7 printer connected to my home network. It works fine with the other two XP computers on the network but after upgrading from Vista to Windows 7 Home it stopped working. I upgraded the drivers and the firmware but there is something with Win 7 that is keeping it from printing. It keeps telling me to turn the printer on; connect the USB cable; or make sure the print queue is online. I disconnected it from the network and connected it directly to the computer with the USB cable and it works fine. So I know the drivers are ok. Anybody have any suggestions? -Ken

If the printer is normally connected directly to the network using an ethernet cable, then you should only have to change the Port setting on the prionter driver to a Standard TCP/IP Port and supply the correct IP address for the printer.

Thank you for your response. How do I change the port setting on the printer and supply the correct IP address. Sorry to be so ignorant, but I really don't understand Windows 7 yet. -Ken

To find out what IP address the printer is using, check the printer driver port settings on a computer that is able to print to it.

Possibly useful links:

http://www.musc.edu/infoservices/lynx/ip_printing.pdf

http://www.region1tech.umd.edu/faq/Printer_Ports.htm

http://technet.microsoft.com/en-us/l...39(WS.10).aspx

The IP address is correct.-Ken

Can you ping the printer's IP address from the Win 7 computer? Also, you could open a Command Prompt window and use the command below to generate a text file of the computer's IP address info. Copy the contents and post it here.

Code:

---

ipconfig /all > ipcfg.txt

---

How do you ping the printer? I ran the command prompt but I can't find the ipcfg.txt file. Where do I look for that? -Ken

To ping the printer, in a command prompt window type: "ping xxx.xxx.xxx.xxx" where the xxx.xxx.xxx.xxx is replaced by the printer's IP address.

The ipcfg.txt should be in the same folder that was showing as the prompt in the command prompt window. You could replace it with C:\ipcfg.txt and it would be in the root directory of the C: drive.

The ping worked. I got a reply all three times. But I still can't find the ipcfg.txt file. I did a search of the whole drive and it isn't there. This is what I typed in the command line "ipconfig /all > c:\ipcfg.txt" is there something that I'm missing? -Ken

Open my computer, open C:\ and it should be near the bottom.
Double click ipcfg.txt and it will open in notepad.

Sorry, it just isn't there.-Ken

start -> cmd (Right click and select run as admin) then the popup stays
Now try the "ipconfig /all > c:\ipcfg.txt"

Finally it worked! Here is the result

Windows IP Configuration

Host Name . . . . . . . . . . . . : vmpierce-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : neo.rr.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : neo.rr.com
Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1E-90-04-15-53
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, March 09, 2010 12:58:30 PM
Lease Expires . . . . . . . . . . : Wednesday, March 10, 2010 12:58:30 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 209.18.47.61
209.18.47.62
NetBIOS over Tcpip. . . . . . . . : Enabled

Is your printer's IP address in the 192.168.1.xxx range?

Yes, it is 192.168.1.100

The IP address looks correct. I suggest trying again to install a network printer. Some possibly useful links are below:

http://lifehacker.com/5262706/setup-...p-to-windows-7

http://www.howtogeek.com/howto/windo...dows-7-and-xp/

http://www.google.com/search?hl=en&s...i=g10&aql=&oq=

Do you have a 3rd party firewall installed? If so, try disabling it temporarily. I've lost count of the times that I've found a firewall at the bottom of this sort of problem.