PDA

View Full Version : IP settings for computer and nfusion



carstunts
10-07-2012, 07:16 PM
Hello,

I get the occasional problem getting my computer to connect to my nfusion and I just want to make sure that my settings are correct. When it works, it works. I am pointed to 110 and 119. Please let me know if there are any settings that I should change. There doesn't seem to be any apparent network conflicts, but on the machine running NOI, sometimes I can't connect to the internet until I disable the onboard lan. I have ping tests that I can run on demand on the machine to check if i can get to google, my router, and the private server. It just seems a bit flaky, like the computer is trying to connect via the lan instead of the wireless for the internet. I usually put the receiver on channel 302 and then wait.

Here's my setup:

Computer -> connects wirelessly to my wireless router (192.168.2.1) with a wireless adapter (DHCP).
Nfusion HD Receiver -> connects to my desktop with a static address assigned to the onboard network adapter and connects with an ethernet cable.

COMPUTER RUNNING NOI - IPV4 SETTINGS
-----------------------------------------

-set to static IP
ip- 192.168.0.101
snm- 255.255.255.0
dg- 192.168.0.1
pdns- 208.67.222.222

advanced ips under IPV4:

192.168.0.101 / 255.255.255.0
123.108.109.22 / 255.0.0.0
123.108.108.138 / 255.0.0.0

ON NFUSION RECEIVER:
------------------------------------
-set to static IP
IP - 192.168.000.120
Snm - 255.255.255.000
gw - 192.168.000.101
dns - 192.168.000.101

Thanks for your help in advance!

meduser
10-07-2012, 08:11 PM
Hello,

I get the occasional problem getting my computer to connect to my nfusion and I just want to make sure that my settings are correct. When it works, it works. I am pointed to 110 and 119. Please let me know if there are any settings that I should change. There doesn't seem to be any apparent network conflicts, but on the machine running NOI, sometimes I can't connect to the internet until I disable the onboard lan. I have ping tests that I can run on demand on the machine to check if i can get to google, my router, and the private server. It just seems a bit flaky, like the computer is trying to connect via the lan instead of the wireless for the internet. I usually put the receiver on channel 302 and then wait.

Here's my setup:

Computer -> connects wirelessly to my wireless router (192.168.2.1) with a wireless adapter (DHCP).
Nfusion HD Receiver -> connects to my desktop with a static address assigned to the onboard network adapter and connects with an ethernet cable.

COMPUTER RUNNING NOI - IPV4 SETTINGS
-----------------------------------------

-set to static IP
ip- 192.168.0.101
snm- 255.255.255.0
dg- 192.168.0.1
pdns- 208.67.222.222

advanced ips under IPV4:

192.168.0.101 / 255.255.255.0
123.108.109.22 / 255.0.0.0
123.108.108.138 / 255.0.0.0

ON NFUSION RECEIVER:
------------------------------------
-set to static IP
IP - 192.168.000.120
Snm - 255.255.255.000
gw - 192.168.000.101
dns - 192.168.000.101

Thanks for your help in advance!

The only thing I can see..

You have:
192.168.0.1 as gateway?

Then on the nfusion you have:
192.168.101.101


The dns on the NFHD is supposed to be set to the router's ip address, in your case:
192.168.0.1

I would try that.

carstunts
10-07-2012, 08:29 PM
The only thing I can see..

You have:
192.168.0.1 as gateway?

Then on the nfusion you have:
192.168.101.101


The dns on the NFHD is supposed to be set to the router's ip address, in your case:
192.168.0.1

I would try that.

My router IP address is 192.168.2.1, so I set my DNS on the NFHD to 192.168.2.1? I've been a little confused about if the receiver communicates on it's own little network or if it communicates only out using my router as DNS to the internet. Is the IP address on the receiver supposed to be outside of the routers DHCP range? Eg: 192.168.2.160. Do I leave the gateway as 192.168.000.101 and the DNS to 192.168.002.001 (192.168.2.1)? Hopefully I'm interpreting this right. Thanks.

EDIT: I ended up changing just the DNS entry on the receiver to 192.168.2.1 and it seems like it is ok. I didn't change anything else and it seems to be working ok. If there is something else I should change, please let me know.

meduser
10-07-2012, 09:41 PM
What I would do is:
change the routers address to 192.168.0.1
then make the dns on the NFHD :192.168.0.1
I would set the NFHD's ip address to static, if my pc was static and set to 192.168.0.101, then I would set the NFHD to be 192.168.0.102(if available)
The IP of the NFHD needs to be inside the routers dhcp range.

so if you set your pc to 192.168.0.101,

the NFHD would be set up as

ip: 192.168.0.102(if available)
subnet:255.255.255.0
gateway: 192.168.0.101
dns: 192.168.0.1(if you set it to that)

done.

meduser
10-07-2012, 10:06 PM
EDIT: I ended up changing just the DNS entry on the receiver to 192.168.2.1 and it seems like it is ok. I didn't change anything else and it seems to be working ok. If there is something else I should change, please let me know.[/B]

same things as what I suggested..lol

what ever works

dishuser
10-07-2012, 10:09 PM
same things as what I suggested..lol

what ever works

you told them to change router ip
not the same thing

meduser
10-07-2012, 11:05 PM
you told them to change router ip
not the same thing
or the alternative is to change the NFHD to the right router ip...same end result of making sure the router ip is entered into the NFHD correctly

carstunts
10-08-2012, 03:37 AM
or the alternative is to change the NFHD to the right router ip...same end result of making sure the router ip is entered into the NFHD correctly

Seems like that was part of it. I stuck with my router IP of 192.168.2.1 because I access work resources sometimes via VPN and my network config needs to be this way. I played around with all these settings all day, even after I thought it was fixed. I figured out that I had to upgrade the driver for my onboard network card (which may have explained why I was experiencing more freezing then normal or S.U.N.S disconnected messages.

These are the settings that seemed to work for my setup (in case if this is helpful for someone else). You might wonder why/how these work, but they do. I'm running r25 bin. I tried selecting an IP out of the DHCP range for my computer but my other devices kept trying to select the IP I was wanting for the receiver. Getting this stuff to work can be frustrating.

On the computer - IPV4 Settings for on-board LAN:

IP address: 192.168.0.101 (static address I assigned to my pc)
Subnet mask: 255.255.255.0
Default Gateway: 192.168.0.1 (just a note, this is NOT my router IP address)

Use the following DNS server addresses: Preferred DNS server - 208.67.222.222 (opendns dns server)

Under advanced: 192.168.0.1 Subnet: 255.255.255.0
123.108.109.22 Subnet: 255.0.0.0
123.108.108.138 Subnet: 255.0.0.0

My Wireless Adapter

I left it as DHCP.

On the NFHD:

IP: 192.168.000.120 (IP address I randomly chose that is not the same network as my router)
Subnet Mask: 255.255.255.000
Gateway: 192.168.000.101 (same static IP address assigned to my computer)
DNS: 192.168.002.001 (this is my router IP)

Hope this helps others!

Mr. Bean
10-08-2012, 07:09 AM
This sucks, just spent the last 20 minutes tell you why it works and what would have been easier and then it didn't even post!

So here is the short version as I don't feel like going through it all again.

Basically, it works because you have, in effect, set up two networks and created a lot more work then you needed. You have a 192.168.2.x network and a 192.168.0.x network.

What you should have done was on the computer select both the wireless and LAN connection at the same time and then BRIDGED them.

You then make this connect and set it static. In your situation it would be the computer would be:

IP address: 192.168.2.101
Subnet mask: 255.255.255.0
Default Gateway: 192.168.2.1
Preferred DNS server - 208.67.222.222 (opendns dns server) (I use 8.8.8.8 or 8.8.4.4 for Goggles DNS)

123.108.109.22 Subnet: 255.0.0.0
123.108.108.138 Subnet: 255.0.0.0

(Those are for 24f or 25f)

or 210.51.47.147 Subnet 255.0.0.0. for 27F)

On the NFHD: (As Static)

IP: 192.168.002.120
Subnet Mask: 255.255.255.000
Gateway: 192.168.002.101 (same static IP address assigned to the computer)
DNS: 192.168.002.001 (this is the router IP)

meduser
10-08-2012, 03:10 PM
Well said.. :)

Lowteck
10-09-2012, 01:02 AM
When my nfusion HD works I have the gateway and the dns pointed to the computer that has NOI running on it. I have never been able to get my nfusion to work with the gateway or the dns as the router ip address.

meduser
10-09-2012, 03:33 AM
When my nfusion HD works I have the gateway and the dns pointed to the computer that has NOI running on it. I have never been able to get my nfusion to work with the gateway or the dns as the router ip address.

I guarantee it works using the router and pc on NFHD...using the pc can work, but I have seen issues with that way to.

I use what I know works, and the way described in some of the other posts above is what works for me.

Lowteck
10-09-2012, 03:33 PM
Apparently both of us each have our own way of using the nfusion. My question is why yours works one way and mine will not. Are you using the NF Network setup program to set your network up? If that is the difference then it would be nice to cut out a step for me.

Mr. Bean
10-09-2012, 04:25 PM
I never used the network setup program as is it very easy to make a couple of of quick edits to the network. If you want to post your settings we can take a look. Likely just something small that you are missing that a fresh set of eyes might be able to see.

carstunts
10-10-2012, 03:16 AM
This sucks, just spent the last 20 minutes tell you why it works and what would have been easier and then it didn't even post!

So here is the short version as I don't feel like going through it all again.

Basically, it works because you have, in effect, set up two networks and created a lot more work then you needed. You have a 192.168.2.x network and a 192.168.0.x network.

What you should have done was on the computer select both the wireless and LAN connection at the same time and then BRIDGED them.

You then make this connect and set it static. In your situation it would be the computer would be:

IP address: 192.168.2.101
Subnet mask: 255.255.255.0
Default Gateway: 192.168.2.1
Preferred DNS server - 208.67.222.222 (opendns dns server) (I use 8.8.8.8 or 8.8.4.4 for Goggles DNS)

123.108.109.22 Subnet: 255.0.0.0
123.108.108.138 Subnet: 255.0.0.0

(Those are for 24f or 25f)

or 210.51.47.147 Subnet 255.0.0.0. for 27F)

On the NFHD: (As Static)

IP: 192.168.002.120
Subnet Mask: 255.255.255.000
Gateway: 192.168.002.101 (same static IP address assigned to the computer)
DNS: 192.168.002.001 (this is the router IP)

I just wanted to say that this worked like a charm with bridging the connections together. I think I was trying this before but I went about it the wrong way. What is strange is my network adapter says "Network Cable Unplugged" but it's still working ok. Maybe that's just what happens when you bridge the connections, I dunno. I notice the NFHD does this sometimes. Thanks again!

Mr. Bean
10-10-2012, 07:22 AM
Glad you got it working. I get that message once in a while, but it doesn't appear to effect how everything runs... usually when I have too many programs running at one time.