Did I fry my WGPS606?

[jcutrone]

I am at a loss. My printserver was working fine with my ATT 2WIRE 3800HGV-b but then I tried to hook up a Netgear 3500 WIreless N router as an access point following instructions on Netgear website. Not only did it not work, but it stopped me from connecting wirelessly to the ATT router, although I could connect by cable. Called ATT tech support, such as it is, and they got me connected wirelessly again. Great. Then I could not print through the WGPS606.

Ran the installation disk (the downloaded verion for Windows 7, and it gets through the first of the processes, setting up the printer to connect with the print server. I go all the way through the process, it detects and connects to the print server, then recognizes the wireless network, allows me to put in the passphrase, then tries to save the print server settings. The I get an error saying that the installation assistant did not detect a DHCP server. The ATT 2WIRE modem/router does use DHCP. Nevertheless, I follow the instructions and enter an IP address, 192,168.1.170 which was the address for the print server when it was still working, and which is within the att range of IP address, 192.168.1.60 through 253, a subnet mask of 255.255.255.0. Then it says it is verifying the settings and finally says the result is successful. I click the next button. It shows the printserver with the assigned iP addess and subnet mask, wireless settings show the SSID for the att router and the security mode for the router, WPA-PSK, I het the next button and it then asks if I want to set up the PC for printing.

However, when I go to the second step, to set up the PC for printing, it is unable to detect the print server on the network. The print server is plugger in for power (first suggestion), there is an ethernet cable conncetion to the printserver (second suggestion) I have then followed the third suggestion, and turned off the firewall for the pc and for the router go through the entire process 8-10 more times but it is never able to connect. I opened the 2wire router through a browser, and added the MAC address of the printserver to allow it access, but that did not help.

The weird thing is that I cannot print even by conneccting the printserver to the computer by ethernet cable which I always could do when I had wireless issues. I can, of course print, by conn ecting the printer directly to the PC and changing the printer's address from the IP address for theprint server, the standard TCP/IP port back to the DOT4 port and it will print, but only if it is directly connected to the computer.

I tried opening the printserver when it was connected to the computer with the ethernet cable but I cannot connect even by putting the IP address (192.168.1.170) assigned to the printserver in the browser address box.

I tried manually resetting the print server by depressing the reset button for a full minute which did appear to reset it at least as far as I could tell form the lights. But when I ran the configuration assistant again, i got the exact same results I described above. I have tried setting it up a gizillion times, maybe two gizillion, but always with the same result.

Any help would be appreciated.

[Jack™]

Maybe the introduction of a second wireless router (the Netgear N3500) mixed up your network.
Difficult to say what ATT support exactly did to get everything working again, but start to check all devices and settings. Use router info pages, ipconfig and ping to get info about DHCP server and all devices in your network.
I haven't any experience installing the WGPS606 under Windows 7, so there might be an issue here. There is no Windows 7 download for WGPS606, but maybe there is no problem using the 2.0 software.

Here's a short TBS for the WGPS606:
Follow the instructions in the WGPS606 Installation Guide and read the WGPS606 User Manual.
Make sure you download and install: WGPS606 Print Server Software Version 2.0.

Check that no software firewall such as Norton is running. You may have to uninstall it completely as, generally, you don't need it when you are behind a router in a private network such as your home network.

It's possible to have an IP conflict when connecting the printer at a later point in time during the (manual?) installation. Reset the print server before starting the software.

Also read this thread: WGPS606 and HP LJ 1020 . It might be that your printer/print-driver is not compatible with the WGPS606:
During the installation of 'Set up a printer' and after at the 'Connect Equipment' step you connected successfully the computer to the print server, you have to connect the printer to the print server (make sure the printer is powered up and the USB cable is OK). If nothing is displayed on the screen "The Print Server Detected the Following Printers", then your printer is in all probability not compatible.

HTH

[jmizoguchi]

ATT 2WIRE 3800HGV-b but then I tried to hook up a Netgear 3500 WIreless N router as an access point following instructions on Netgear website.

For one, I would use 2wire 3800 as bridge mode and use 3500 as main router

http://www.sbbala.com/uverse/pg2.html

he I get an error saying that the installation assistant did not detect a DHCP server. The ATT 2WIRE modem/router does use DHCP. Nevertheless, I follow the instructions and enter an IP address, 192,168.1.170 which was the address for the print server when it was still working, and which is within the att range of IP address, 192.168.1.60 through 253, a subnet mask of 255.255.255.0.

make sure that if you are using 2wire is still going to be main DHCP the temporary unplug the 3500 and try again

The weird thing is that I cannot print even by conneccting the printserver to the computer by ethernet cable which I always could do when I had wireless issues. I can, of course print, by conn ecting the printer directly to the PC and changing the printer's address from the IP address for theprint server, the standard TCP/IP port back to the DOT4 port and it will print, but only if it is directly connected to the computer.

did not specify type of printer is used with WGPS

[ron351]

I just got done setting mine up after 6 hours of trouble and had the DHCP also, and I think what solved it was putting the modem in bridged mode.
That is when it seemed to just connect on its own after doing this.