Unsolved
This post is more than 5 years old
10 Posts
0
6751
February 23rd, 2009 15:00
IP address lost after PC restart using Pro/100 Adapter
PC1: Dell Dimension 3000 connected via Pro/100 VE Network Connections adapter, Windows XP SP3
PC2: Windows/ME normally connected wirelessly via WUSB11
Router: Linksys BEFW11S4 v4 firmware 1.52....
Printer: Wireless HP 6988 at 192.168.1.40
Problem: After the PC is restarted, the IP address of the printer is unavailable. Pathping to it shows that the messages do not get past the router. After a router power-cycle, address becomes available
Diagnostic steps done:
- PC2 wireless can see printer address via wireless connection AND via a XIRCOM Ethernet 10/100 adapter to router all the time.
- PC1 can see the printer all the time if connected wirelessly
- Pathping from PC1 (Pro/100 connected) shows NO successful packet beyond Hop 0 until the router is recycled. The it has access to printer. Yes, I tried different connection ports in router.
- Pro/100 is current according to DELL site, but I upgraded it from 7.1.12.0 to 8.0.47.0 via Intel site download. No change to status of problem
Can we conclusively say the Pro/100 board is shot? Intel Diagnostics show no problems. Or do I need to set something other than defaults in the Pro/100 to get it to recognize the wireless printer? Note, all wireless PCs are found. Only the 6988 wireless printer losses address. I tried static addresses BEFORE DHCP range, within DHCP range (i.e., one that never get assigned to anything else), and now above the range.
Any help greatly appreciated.
PudgyOne
9 Legend
•
30.3K Posts
0
February 23rd, 2009 16:00
tpanc13,
What do you get when you use these settings in your wireless router?
Update the firmware in your wireless router. Manufacturer's website, make & Model needed.
Broadcast SSID(You may want to change this to make it easier to connect)
Use WPA-PSK(TKIP) Security(WPA Personal). Most wireless devices work best with this type of security.
Mixed b and g mode(n if available)
Use channels 1, 6 or 11. Most devices work better on these channels. (I use channel 11)
Save and exit. Power everything off for 30 seconds. Power everything back on, wait 30 seconds, now try to connect.
Rick
tpanc13
10 Posts
0
February 23rd, 2009 21:00
Hi Rick,
BEFW11S4 is B only protocol. Only wireless devices on network are PC2 (using b only adapter) and 6988 printer set to use only b protocol.
Already tried Broadcast and no broadcast
Use WEP 64-bit and all wireless can communicate as well as PC1 wired-to-router and PC2(wireless -- file sharing). WEP does not come into play with PC1 hardwired and problem is identical with network configured without WEP. Remember, PC2 connected hardwired via its XIRCOM adapter has no problem finding printer. Channels do not come in to play with Infrastructure mode, only ad hoc. Regardless, router, PC2 and printer are set to use channel 6 should I change to ad hoc network. I think that covers your questions. Just in case you are curious, the problem occurs without antivirus (AVG), without firewalls (XP and ZA), without XP Defender.
The mystery is only the PC with the Pro/100 fails to see 6988 wireless printer address although it has no problem seeing and communicating with wireless PC2. I am waiting for a friend to bring his XP laptop over so we can eliminate XP code from the equation Do not know Network adapter in his.
I really need to know why just a wireless printer IP address and no others cannot be pinged upon a PC restart (Pro/100 adapter only). What is so unique about a printer address? Pathping out acknowledges name "6988" (known to PC and configured in printer) and associates it with address (192.168.1.40), but the remainder of the output shows 100% unsuccessful packets between Hop0 and 1. Of course, after cycling router, pathping is successful, as is printing to the printer.
What can be stopping pathping from completing route? I am pretty convinced it is not the router since I can successfully communicate to printer when I use PC2 either with network cable connect or wireless. And, yes, I tried all ports on the router and different cables, all of which work with other PC.
Would reinstalling TCP/IP and other network protocols possibly clear things on the pro/100 PC? What could be corrupt that locks out only a wireless printer and not wireless PCs. Don't know if I posted this, but I tried 3 different IP addresses for printer (...10, ...25, ...40). This has to rule out corruption of a single address. Wouldn't you think so?
Thanks for quick response. Please, if you can think of anything else, post back.
tpanc13
10 Posts
0
February 25th, 2009 13:00
Cause of this problem is an incompatibility between HP 6988 WIreless printer and Intel Pro/100 ve NIC. See work around at http://www.dslreports.com/forum/r21815028-HP-6988-wireless-connectivity~start=50