Discussion Locked

Server 2003 and Linksys Router

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

OK I am new to Windows Server 2003 but I can't get something that seems basic to work and I feel like I have checked all the logical things. Here is my situation:

Original Setup: Linksys router with DHCP enabled. 1 WinXP machine (Single NIC) plugged direct in to router. 2 laptops connecting via wireless. Everything works perfectly.

Decided to learn more about windows server, so I formatted the WinXP machine and installed Win2003 SBS instead. Now as a server, it won't get an IP address from router. I can't even pull up admin screen at http://192.168.1.1 (router IP).

I removed the DHCP component thru add/remove to make sure it wasn't getting confused. I have also given it a static IP of 192.168.1.2 and told it to look at 192.168.1.1 for DNS. Ultimately that?s what I want since I?d like to be able to hit it from the laptops. Same results either way.

Here has been my plan of attack so far:

1) Eliminate the router and plug net cable from cable modem directly into server. Do ipconfig /release and /renew and bling instant IP from my ISP. I can hit the internet no problem. That test seems to eliminate a problem with network card or driver.

2) Plug this back into internet port on router. Unplug cable from router to server and plug it into my laptop instead. Disconnect from wireless and connect over wire. Release and renew and everything works fine, admin screen, internet etc. That seems to eliminate an issue with the cable or the router port.

3) I read online something about a firmware incompatibility with the router and SBS. Figured what the heck. I have a WRT54G v5 that is now on firmware 1.1.0.9. Didn?t change a thing.

Any ideas on where to go next?

Thanks!

4 replies

by dumphrey

Not sure what you are trying to do, but I would set up dhcp on the router, and exclude an address for the Server. Give the server a static ip address, point at itself for DNS, and provide it as the DNS server in the router config. Configure the server's DNS to forward to the DNS servers of your IP, get off an other machine pluged straight into net connect. Basicly, every machine but router should be looking to server for dns. Router should be default gateway for all machines. All machines on DHCP but server. Server address excluded from dhcp pool. Create your domain and add accounts and machines to it. (note: XP media center and XP home can not join domains).
Hope this helps, if not lemme know.

by hal 9000

I would do as the above poster suggested.

But first flash the FIRMWARE in the Router to the latest available from here

http://tinyurl.com/lad6z

It's version 4.30.5 and with any router it's always a good idea to keep the Firmware up to Date as this is what blocks intrusion. The Manual & directions for upgrading the Firmware are here

http://tinyurl.com/8jun2

But if you allow the Router to assign the DHCP i should be a straight forward install from there.

Col

by jasonit

Thanks for replies... just now back to working on this.

HAL - I already updated it - point 3 above. Per Linksys website I have the latest. Router status info shows May 2006 version.

ISAAKD - I think I am at a much more basic level. From my laptop via wireless I can ping router and get responses. From the server I can not. I would like to use a static IP on server as you suggest... however for testing, if I set server to get IP and DNS dynamically and plug network cable direct from internet, everything works perfectly. But if all I do is plug internet to router and server to router, I get nothing. Can't ping router at all. It eventually gives up and gives me a 169 IP address. What would keep it from seeing the router AT ALL?

That's why I tried to isolate the problem as described above because it seems like something at a very basic level is wrong. But it isn't the NIC (since the server can hit the internet when the router is bypassed), it isn't the cable (since my laptop can connect via same cable), it isn't the router (since laptop can connect via router whether connected on the wire or wireless), the same PC worked in the same setup with WinXP on it.... so it seems like it must be something I have setup wrong in Windows Server.... but what???

by ferzam

Hi Jason, I had exactly the same situation and this is how I fixed it.

- I checked for the Local Area Connection Properties.
- I only left those services that are set up in Windows XP by default (Client for Microsoft Networks, File and Priter Sharing, and TCP/IP)
- Among the services I uninstalled was the Network Load Balancing, which probably was the one in conflict.

After I uninstalled all the protocols I inmediatly got an IP Address.

I hope it helps! =)

This discussion is closed to new replies.