Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FurryNutz]

Is the wireless console wirelesslly connected to the modem? That would be reason why the DNS is showing the modems DNS and not the 655s DNS.

Remember your in a double NAT condition. Be sure the console is connected to the 655 if thats where you wanting it to connect.

[Lone Wolf]

Yes 100% sure connected to the DIR-655, the wireless on the modem is disabled.

[FurryNutz]

Ya, odd that the DNS is 0.1 and not .1.1 from the 655...should be from the 655. Can you run a wired cable to this 2nd console to test to see what it gets on wire?

[Lone Wolf]

Ok just a quick update:

DNS relay is disabled, and I restored the network settings to factory default on both consoles, and both consoles now show the ISP primary/secondary DNS server IPs in the network config section

I played an hour of BF3 on the wired console with no issues, and my son played an hour or so of Halo 4 on the wireless with no screaming (which means it didn't disconnect)

I will try wiring both consoles but I've loaned my extra long ethernet cable to my bro at the mo so can't do this for a while.

I haven't had time to check for quicker DNS servers yet but those apps look good

[FurryNutz]

Sounds good. Yes, sometimes the networking on 360s gets hosed up and is the cause of many NAT status issues. Sometimes doing a factory network reset on the consoles clears this issue up. Hope it keeps working well.