This way they can come in and assess the situation, take inventory and get a first hand look at the way everything is wired (I got lost with yourĭescription at the daisy chaining part), machine configurations, IP addresses, etc. I think it sounds more like you need a local qualified IT consulting company to assist you at this point. If the server and all machines are set to a different IP subnet, then that would definitely cause a problem. You would probably also need to set it up to the the ISP's settings on the WAN side, too, connecting to the modem, and what tyupe of modem you would have would depend on the ISP.
Plus it's DHCP service was just turned on, and possibly conflicting with the server's DHCP, that is if it's installed on the server, and so if any machines are set to DHCP, then they now possibly have a new IP based on the router's DHCP or conflicting results
Resetting the router set it back to default, if I'm not mistaken, the LAN IP of the router is now probably 192.168.0.1 or 192.168.1.1, and the username and password to get into it would be a blank username, and a password of This posting is provided AS-IS with no warranties or guarantees and confers no rights.
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Is the Netgear a switch or a router? I assume it's a 16 port switch from your original description. I assume the server is running DHCP? Go into Services and see if the "DHCP Server Service" is running (leave the one that says DHCP CLient Service alone - that needs to beĪctually, go into a cmd prompt, and run a net start > c:\netstart.txt Open the netstart.txt file and copy and paste the results here.ĭo the same for an ipconfig /all > c:\ipconfig.txt and open the c:\ipconfig.txt and copy/paste the results, please. Ok, now that you have the wireless router password, go in and disable DHCP in it. Thanks in advance for any help anyone can give leaving them in a lot better shape than I found them. Ideally if I can solve all their server admin problems I can document pass codes etc. Is it a possibility that the Server is gate keeper for the incoming broadband signal? I know this info is lacking a lot of detail but if you can ask meĬlarifying questions I might be able to better describe the situation.
I tried bypassing the wireless by plugging the modem directly into the netgear box but no love. Sending signal fine, but the linksys router dead ends, I haven't checked the out on the netgear router but I suspect the is a issue with the Server but maybe that is me being paranoid of the fact that that is the only part of the equation I can't reliablyĭiagnose. But when I hit the reset on the linksys router the whole network went down.
So in walks me, more nerve than brains I've learned my limitations so I made it a point to only mess with what I knew how to fix.
The last person to set up their wireless also did not write down the wireless password for them so they have not had access Had daisy chain set up that went from the modem, to a Linksys WRT110 wireless router, then another cat5 to the netgear router 16 box. I personally have little experience with server 2003, I figured out how to add users to their existing structure and give them the restrictions they requested, but that is where my skill set ends. The only access is the server box pass word itself. The person that set it up failed to leave the company the Admin pass word and Here goes: I have a client that has an older WinServer2003 r2 box that has user restriction all over it. Well I hope I can describe this issue clearly enough to be understood.