Thursday, June 25, 2009 1:58 PMJust wanted to say that Windows 7 has been great to me, so far, on several machines under different conditions. This is the first issue I've come across that I wasn't able to figure out or research a solution for and I've been testing W7 RC1 in the lab for a good few weeks. Keep up the good work!
Now, onto the problem:
I'm trying to install an HP Laserjet 4000n (network printer with internal LAN interface) on an HP DV6633US laptop.
The laptop has 1 wired LAN interface:
Realtek RTL8101E Family PCI-E Fast Ethernet NIC (NDIS 6.20)
and one wireless interace:
Intel Wireless WiFi Link 4965AGN
The network I'm using is set to a "Home network" in the network and Sharing Center console with no obvious restrictions being imposed in any of the settings I have found so far (all discovery and sharing options are enabled).
I have no problems connecting to various network shares on the peer-to-peer test environment. After attempting to install the printer (using the wireless interface) and noticing considerable durations for the detection steps (and print failure), I tried pinging the IP of the printer with 100% loss. After poking around a bit, I noticed that I can ping the IP address via the wireless interface without any issues if I use the administrator console (command prompt run as administrator). So I can ping the address from the admin console, but not the standard user console. However, If i connect to the network via the wired interface, I can ping the address just fine in either console. This behavior exists regardless of the firewall state, with the windows firewall being the only firewall currently installed on that machine.
Am I missing something here? I apologize for the scatter-brained post, I was up all night working on something so I haven't gotten any rest yet.
Thanks in advance!
***edit: I forgot to add that both adapters are setup to use the same basic configuration info (ip, subnet, etc), but only one is being used at any given time.
Thursday, June 25, 2009 2:20 PMHave you installed this driver for the printer? Or did Windows update find one for you?
Thursday, June 25, 2009 2:45 PM
Hi Adam, thanks for the quick reply!
I have tried the current printers from the HP support website as well as the driver for the 4000 series from windows update. When it does print on the wired adapter, it throws a PCL XL error so I know I'm going to have to probably scale back to the PCL 5 drivers from teh website like a few other people have done in other forums. Any idea why I wouldn't be able to ping from the standard console by any chance?
Thursday, June 25, 2009 7:36 PMIn other weird news... Now I can't ping the printer's IP from the admin console on the wireless adapter either, but I can ping/print just fine on the wired adapter.
Saturday, June 27, 2009 4:49 PMIt is probably still a driver issue. Did you try a wireless driver from Intel's website?