MariHD,

Were you able to get through all twelve steps in Chapter 5 "Windows Driver Installation", in the PSUS4 User Manual? Steps 11 and 12 change the printer driver setup to use the print server instead of the local USB connection.

Jim

jimw,

Thanks for the quick response.

When I was installing the Linksys print server driver, I had to have the laptop wired via Ethernet to the print server (otherwise, it would not recognize it). It said it installed OK, so I made the assumption all was well.

However, as you point out, now I need to tell the print server I am trying to communicate to it through the Cisco AP. Correct? That is where I must be going wrong?

It seems then maybe I should reinstall the print server driver and when I get to step 11/12 unhook the ethernet and try to connect??

As you can tell, I am not sure of the exact sequence of steps I should follow....but I can try tomorrow and let you know (I am currently working one hour away from my "problem" machine) Thanks again.

MariHD,

As far as IP addressing on your LAN is concerned, the Aironet 1100 is a "passive" device. While it may itself receive an IP address from the Direcway Modem/Router, it doesn't issue any IP addresses. The Direcway issues IP addresses to all connected devices on your LAN, whether they're wired or wireless.

When you configured the PSUS4, it should have been connected by Ethernet to a LAN Ethernet port on the Direcway. That way it will receive an IP address from the Direcway. The printer should be connected to the USB port on the print server.

I'm not sure how the installation worked at all if the PSUS4 was connected via Ethernet to your laptop. Where would the PSUS4 receive an IP address from if it were connected that way?

The Linksys installation software should have been able to locate the print server while it was physically cabled to the Direcway, since the PSUS4 would be assigned an IP address on the same network as your laptop. That's true in spite of the fact that your laptop was connected wirelessly.

If you tried that and it didn't work, we'll need to take a closer look at the way the Direcway's Ethernet ports work, and also at the built-in DHCP server in the Direcway. Without knowing the model number of the Direcway, I'm making lots of assumptions about the way it works. If you'll post the model number of the Direcway, I'll see if I can find a manual for it.

Jim

jimw,

I have a Direcway DW 6000 modem (Consumer Edition). Here is a link to the manual.

http://www.virgintechnologies.com/start.asp?main=DiRECWAY_Software.htm

(The Direcway site requires user id & password, so I didn't link you there)

Maybe I should also clarify my network setup (my phrasing was confusing).......

From the DW6000 modem, I have an Ethernet cable to one port of the Linksys print server/4 port hub. Then, in another port of the hub, I have my Cisco 1100 AP connected with Ethernet cable. In a third port of the hub, I have a desktop computer (a Gateway). That leaves one port open.....

Finally, my HP 2210 multifunction is connected to the Linksys with a USB cable.

To further clarify, when I was initially installing the Linksys software on my new laptop, I had to connect to the 4th port of the Linksys with an Ethernet cable. The print server would not recognize my laptop unless I was physically connected...
I DID NOT disconnect the print server from the DW6000 modem.

So, right now I can still access the internet, but still stuck on the printing part....Thanks again for further help...

MariHD,

OK, my drawing has been corrected. Thanks for the clarification, and the link to the Direcway manuals.

The short description of the problem is that the print server installation software is having difficulty finding the print server if the laptop is connected wirelessly. The way the print server software "finds" the print server isn't clear from the Linksys documentation. If it's scanning the network for a device that responds the way the print server is expected to respond using the range of IP addresses defined by the network adapter's (either one) IP address and subnet mask, it should be able to find the print server. Since the way the print server has been connected has not changed (it's always been cabled to the DW6000), it shouldn't matter whether the connection is the wireless one or the wired one.

I was hoping the DW6000 manual would provide more detail about the way its DHCP server works. It would be useful if there were a status display in the DW6000's Web server that showed the DHCP lease status of all connected DHCP clients as well as their IP addresses. There's nothing in the manual that shows how to do that!

It would be particularly useful to know the IP address of the print server, since it also has a built-in Web server. With the IP address, it would be easy enough to check that the print server is reachable through both the wireless and wired interfaces. Even knowing the range of IP addresses that the server will assign to clients would be useful, but that's not documented.

So let's do some detective work...

Connect the laptop to the print server via Ethernet. If you haven't already installed the "Bi-Admin" management utility described in Chapter 8 of the PSUS4 manual, install and run it. It should be able to find the print server (see p. 29 of the Linksys manual). The main display lists the print server's IP address, subnet mask, and gateway address. Record all those. Then exit the Bi-Admin utility. In a cmd.exe window, (Start/Run cmd.exe), type ipconfig /all. Record the IP address, subnet mask, and default gateway assigned to the Ethernet card. Then disconnect the Ethernet cable and enable the wireless adapter. Once the wireless adapter has received an IP address, again type ipconfig /all in a cmd.exe window, and again record the IP address, subnet mask, and default gateway. The last two should be the same and the IP address should be different than the one for the wired interface.

Again run the Bi-Admin utility. Can it find the print server? It should be found at the same IP address as before, since nothing in its configuration has changed. If it cannot, can you "ping" the print server using its IP address? That's also done from a cmd.exe window, using the command ping (ip address of printserver). Substitute the IP address of the print server reported by the Bi-Admin utility for (ip address of printserver). If the ping works and the Bi-Admin utility can't find the printer, then we're dealing with something that's blocking the way the Bi-Admin utility and the print server installer "discover" the print server.

One way could be the Windows firewall, or another firewall installed on the laptop. If it's disabled on the wired interface and enabled on the wireless interface, that would explain the problem! Is it?

(edit) One more observation: If the print server is configured via the wired interface, you should not need further configuration for the wireless interface, since it's the print driver that's making the connection, independently of which network interface is in use. And one more question: Can you print to the HP 2210 via the print server when the laptop is connected through its Ethernet interface?

(edit 2) Clarified the use of the "ping" command.

Jim

Message Edited by jimw on 12-09-2004 04:45 PM

Message Edited by jimw on 12-09-2004 04:50 PM

jimw,

Thanks for such a detailed answer, I believe I understand clearly what you are asking......now on to the detective work!

I am out of town and plan on being able to begin my "detective work" when I return on Sat. afternoon.....sorry to keep us in suspense so long :))

I'll respond as soon as I can.

Thanks again, I look forward to figuring this out....