 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows XP / Networking and Web / October 2004Netgear PS100 Print server ... how to set network to make work?
I'm having trouble getting this new device to work. Have sent emails to Netgear Support, but they are not responding. Disappointing. My hunch is that the root cause is network settings on the computers trying to access the device. The setup wizard doesn't detect the device, and I can't ping the device at 192.168.0.150 which I understand is the default address. All LED's on the device, and on the hub to which it's connected are lit, so I conclude that it's working from a hardware persepective and it's sofware config. All the devices on our network are in 192.168.1.n range, with netmask of 255.255.255.0. The PS100 is 192.168.0.150. My hunch is that my netmask make its so the 192.168.0.150 range is not accessible. I need to change that address on the device, but I can't change it until I can access it at least once. Is it the netmask on the XP laptop I'm using to try to ping it? I'm at 192.168.1.49 with netmask 255.255.255.0. How to make this laptop be able to access this device? rms > I'm having trouble getting this new device to work. Have sent emails > to Netgear Support, but they are not responding. Disappointing. [quoted text clipped - 3 lines] > device, and I can't ping the device at 192.168.0.150 which I > understand is the default address. I was curious so I did a lookup on the Netgear website - "NETGEAR PS100 Series Print Server is set with the factory setting for DHCP environment, which means if you have a DHCP server (most recent broad band routers have provided this feature), PS100 Series will get its own IP address settings for TCP/IP. " What do you have doing DHCP serving on your network? > All LED's on the device, and on > the hub to which it's connected are lit, so I conclude that it's > working from a hardware persepective and it's sofware config. > > All the devices on our network are in 192.168.1.n range, with netmask > of 255.255.255.0. The PS100 is 192.168.0.150. How do you know that? > My hunch is that my netmask make its so the 192.168.0.150 range is not > accessible. > I need to change that address on the device, but I can't > change it until I can access it at least once. Yep. > Is it the netmask on > the XP laptop I'm using to try to ping it? I'm at 192.168.1.49 with > netmask 255.255.255.0. How to make this laptop be able to access > this device? http://kbserver.netgear.com/support_details.asp?dnldID=205 might have more info. > rms Lanwench, Thanks for your input ... A good catch re DHCP. see embedded: >>I'm having trouble getting this new device to work. Have sent emails >>to Netgear Support, but they are not responding. Disappointing. [quoted text clipped - 12 lines] > > What do you have doing DHCP serving on your network? I have a Linksys router as DHCP for network. Ah ... but you make a good point that didn't twig with me. My device gave it the IP, not the default (see next). >>All LED's on the device, and on >>the hub to which it's connected are lit, so I conclude that it's [quoted text clipped - 4 lines] > > How do you know that? I know that because that is what is documented in the manual. However ... your point about DHCP was a good one that I missed. (Slapping head). I re-started the printer server device, and then I looked at the DHCP addresses that were handed out by router ... gave 192.168.1.50 (which is the first available IP). I could only be that device. Progress. Pinging the device got a response. Even more progress. >>My hunch is that my netmask make its so the 192.168.0.150 range is not >>accessible. [quoted text clipped - 10 lines] > http://kbserver.netgear.com/support_details.asp?dnldID=205 might have more > info. Thanks ... I found this document, but cleary didn't absorb everything (re the DHCP address assignment). I'll re-read. I'm at the point where I can ping the device, but can't get the Netgear wizard to discover it, and using http:\\192.168.1.50 to access it (per the manual) also doesn't work. Something else going on. I'll re-read the doc in more detail. Thanks! >>rms > Lanwench, > > Thanks for your input ... A good catch re DHCP. No prob.... > see embedded: you, too... >>> I'm having trouble getting this new device to work. Have sent >>> emails to Netgear Support, but they are not responding. [quoted text clipped - 34 lines] > device. Progress. Pinging the device got a response. Even more > progress. >>> My hunch is that my netmask make its so the 192.168.0.150 range is >>> not accessible. [quoted text clipped - 17 lines] > Netgear wizard to discover it, and using http:\\192.168.1.50 to > access it (per the manual) also doesn't work. Try http://192.168.1.50 - presuming that's the right IP. Run ipconfig on your workstations to make sure you aren't trying to access something else. > Something else going on. I'll re-read the doc in more detail. > > Thanks! No prob -hope it works. >>> rms Neither http:\\192.168.150 nor http://192.168.1.50 gets any response. (timeout error) Pinging 192.168.1.50 does work. Reported .. yet again to Netgear support .. I hope they don't continue to ignore my email requests. Wish there was a way to phone them (but they say phoning is only for USA and Canada which I'm not in). Thanks, rms rms >>Lanwench, >> [quoted text clipped - 77 lines] > >>>>rms > Neither http:\\192.168.150 nor http://192.168.1.50 gets any response. > (timeout error) > > Pinging 192.168.1.50 does work. But you don't know for sure that's the IP address. Can you ping other computers on your LAN? If you disconnect all but your computer and the print server from your router, you should see the connected devices listed - then try the one that isn't yours. > Reported .. yet again to Netgear support .. I hope they don't continue > to ignore my email requests. Wish there was a way to phone them (but [quoted text clipped - 87 lines] >> >>>>> rms Yes, I do know for sure it's the right DHCP address on the PS101 printers server as it is the only device using DHCP. All other computers are using defined IP's. I changed the XP laptop from DHCP to defined IP specifically for this. On the router/dhcp server, I killed all DHCP connections, then restarted the print server PS101. When restarted it came in as 192.168.1.50. (from your advice I was able to notice this.) I can ping this device from all machines, and all machines can ping each other. The network works. My hunch now it has flawed firmware or a or something on the PS101 ... because while it seems to ping, it doesn't announce itself as a print server to the Netgear configuration software. I conclude this because I even can't get to it via the HTTP interface via XP or Linux. Other than power off/on, there is no apparent way to reset the device. I started this journey thinking it was my fault. I now conclude it's the device's fault. I've sent another email to Netgear. Hope they respond. (My kids are bugging me ... "Dad, when can use the printer?" ... wonderful being end use support for the family!. The pressure!) >>Neither http:\\192.168.150 nor http://192.168.1.50 gets any response. >>(timeout error) [quoted text clipped - 97 lines] >>> >>>>>>rms > Yes, I do know for sure it's the right DHCP address on the PS101 > printers server as it is the only device using DHCP. All other [quoted text clipped - 4 lines] > able to notice this.) I can ping this device from all machines, and > all machines can ping each other. The network works. Hokay. > My hunch now it has flawed firmware or a or something on the PS101 ... > because while it seems to ping, it doesn't announce itself as a print [quoted text clipped - 3 lines] > the device. I started this journey thinking it was my fault. I now > conclude it's the device's fault. There's probably a way to do a hard reset on the device to force it to return to factory defaults - check the documentation. If that doesn't work, return the device. > I've sent another email to Netgear. Hope they respond. > > (My kids are bugging me ... "Dad, when can use the printer?" ... > wonderful being end use support for the family!. The pressure!) Tell them you've decided to implement a paperless office. ;-) >>> Neither http:\\192.168.150 nor http://192.168.1.50 gets any >>> response. (timeout error) [quoted text clipped - 99 lines] >>>> >>>>>>> rms |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.