New Router - Netgear WNDR3700

[computer33]

Well, just upgraded my router to a Netgear WNDR3700 from an ancient Lynksys. Now my 2 clients will not connect to the Sage server. I tried typing the ip and the server name and neither works. I can ping the ip successfully and navigate the servers shared folders fine. The HD100 can connect just fine.

Where do I start to troubleshoot this?

[tmiranda]

This won't be much help, but I have the same router and it works just fine. Some things to consider:

First thing I'd do is look at the "Attached Devices" (under "Maintenance" in the left panel of the router's config menus) to see if the client machines show up.

When you say you tried typing the IP and server name, where are you typing from? From the client machines can you ping the server?

Do you have the Sage Clients set to automatically connect to the server? If yes, it won't work if the server's IP address changed. Go look in the client .properties file and delete the line that has the server's old IP address. (I forget the exact line at the moment, just search the .properties file until you find the IP address in there.)

[gplasky]

Since you installed a new router your server and other machines probably have new IP addresses. Double check your IP you are using to connect on the server.

Gerry

[Skybolt]

Not sure if this is what Gerry ment but, check your IP address of the Sage server. Linksys and Netgear use differant DHCP ranges, perhaps you have an overlap? Also make sure the Sage server can reach the internet, in most case's this means your routing is correct - for most home networks anyway.

-Skybolt

[SHS]

Under LAN Setup link you need Change your DHCP Server ranges 192.168.1.2 on Starting IP Address to higher number like 192.168.1.100.
Or reset all your PC back to Full auto and used Address Reservation by add SageTV Server to IP that you want problem solve.

[computer33]

Originally Posted by tmiranda

This won't be much help, but I have the same router and it works just fine. Some things to consider:

First thing I'd do is look at the "Attached Devices" (under "Maintenance" in the left panel of the router's config menus) to see if the client machines show up.

When you say you tried typing the IP and server name, where are you typing from? From the client machines can you ping the server?

Do you have the Sage Clients set to automatically connect to the server? If yes, it won't work if the server's IP address changed. Go look in the client .properties file and delete the line that has the server's old IP address. (I forget the exact line at the moment, just search the .properties file until you find the IP address in there.)

Attached Devices always comes up blank for me. Only once did it actually list anything. I believe that is a known problem with these routers. I have a V2 router if that makes a difference.

Uninstalled the client then deleted any trace of sage files and then re installed and still no luck? I am pinging the server from a command prompt so I know the IP has not changed and I can remote desktop connect to it from its ip address.

[computer33]

Originally Posted by gplasky

Since you installed a new router your server and other machines probably have new IP addresses. Double check your IP you are using to connect on the server.

Gerry

Double checked and triple checked and it's 192.162.1.8. I know that's it because i can remote desktop connect with this ip address to the server machine.

[computer33]

Originally Posted by Skybolt

Not sure if this is what Gerry ment but, check your IP address of the Sage server. Linksys and Netgear use differant DHCP ranges, perhaps you have an overlap? Also make sure the Sage server can reach the internet, in most case's this means your routing is correct - for most home networks anyway.

-Skybolt

Server ip is 192.168.1.8 and that is what i type at the clients prompt every time. Server can connect to the internet fine. All clients connect to the internet fine.

[computer33]

I am convinced it is a router thing because 2 laptop clients can't connect. Puzzling why the HD100 does not mind the new router?

Hmmm... what next.

[KeithAbbott]

Maybe port 42024 is blocked in the router settings?

http://forums.sagetv.com/forums/showthread.php?p=105335

[Protoman]

I'd like to throw a monkey wrench in, and just say that this is the router I have. More specifically I have the WNDR3700 v1 version, and have had next to no issues with it. I have also been able to stream SageTV content across the Internet, and also use SageTV wirelessly with no issues.

There are several things I would do to make sure your setup is rock solid. First, I would make sure you have the latest firmware from Netgear. Second, I would either do a Static IP Address on the SageTV Server or DHCP Reservation.

One thing I have done is used DHCP Reservations and assigned my SageTV Server to 192.168.1.100. This way I can still use DHCP, but my server will always have the same IP Address. Also, port forward 31099 so you can stream SageTV over the Internet if you want.

I would share screenshots, but that would mean reconfiguring my entire network again, since I have recently complicated it by adding a Unified Threat Management device into the mix.

Hope this helps.

[Skybolt]

Originally Posted by computer33

I am convinced it is a router thing because 2 laptop clients can't connect. Puzzling why the HD100 does not mind the new router?

Hmmm... what next.

I didn't notice, but are you using wireless? If so try no encryption at first then turn back on.

Good luck, let us know what you find.
-Skybolt