Laptop has wired and wireless connectivity issues (DNS?)

[IcyTea]

I first accidentally posted into Wireless Networking without thinking, so I manually relocated it here.
The past few days have been very hard. The internet's been on and off, and windows diagnostics say that I have DNS problems or nothing at all. I have comcast internet. I've tried many things to fix it, such as using public DNS servers and power cycling the modem. I have a model SBG6850 as a modem-router. I believe that this is only occurring on this one laptop. This is the current status of it.

Specs:

• 
  ■ Model SBG6850
  ■ LAN adapter - Killer e2200 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
  ■ Wireless adapter - Killer Wireless-N 1103 Network Adapter
  ■ Network splitter for cables, 2 -3.5dB output and 1 input
  ■ Windows 7 64bit home

Here are the things I've already tried.

• 
  ■ 4 cmd lines: (ipconfig/flushdns, /renewdns, /releasedns, and something else)
  ■ powercycling the modem
  ■ using public dns servers
  ■ running namebench
  ■ right-clicking and using the "diagnose button" (it either says that I'm configured correctly but the DNS server is bad, or that nothing is detected)
  ■ using KillerCleaner (apparently it deleted the drivers for my Killer devices, but I already had the driver pack from Killer downloaded and ready to install, so that was a close call)
  ■ reinstalling killer drivers
  ■ using a different ethernet cable
  ■ restarting my computer
  ■ unplugging the cables and the splitter

I have no idea what the downstream bonded channels are, but I feel like they may be part of te problem.
Any help would be extremely appreciated, as this has been bugging me and getting in the way of a lot of things. Thanks in advance!

 

[scout_03]

did you try wired not using the splitter ?

 

[IcyTea]

did you try wired not using the splitter ?

I thought about it, but I was reluctant to do so, because I read somewhere that it provided too much power to the modem. I guess there really isn't a reason not to, though. I'll try that right now. If I have any problems, I'll probably update this.

 

[scout_03]

it could be a part of the issue .

 

[IcyTea]

it could be a part of the issue .

Thanks a lot for the response, though. It's much appreciated I was afraid that I'd be stuck waiting for it to go away or forced to call someone to come over here. I'm probably going to come back if it fails, or in 24 hours without failing. Again, thanks
UPDATE: I just had the idea of checking the the diagnostics and this popped up

Would this still be of any concern?

 

[scout_03]

your welcome .

 

[IcyTea]

your welcome .

Even though I haven't disconnected yet, one thing still piques my curiosity: Why did this just spontaneously happen? It wasn't a problem for me for a long time, yet this just suddenly happens out of nowhere. It would be interesting to know why.

UPDATE: 1 minute after posting this, my internet just crashed twice within one minute. I guess it's still here.

 

[scout_03]

the system is plug directly to the provider modem so you need to check your settings and see with them why you get disconnect callling the service department they may change the modem if it is defective .

 

[pzzlmstr]

I got exactly the same error.
My laptop connects wirelessly and does DHCP and gets a valid IP and gateway, but the DNS ip address is messed up. All my other wired devices get my ISP's DNS server ip address (75.75.75.75 - comcast's DNS) - but my laptop gets 192.168.1.250 ... strange.

I could not figure it out!!

I finally gave up and reconfigured the IPV4 on that device to (a) get the IP address through DHCP automatiocally -- but to hardcode the DNS addreses. I did a ipconfig /all on my other computer and got its DNS addresses. then I hard coded those intot my laptop and BINGO !!! it works fine

problem is , if I take my laptop somewhere else, it may not work (but I rarely do that).

I never had to do this before, it only started recently. I suspect some patch or hotfix from Microsoft. I have a workaround so I am semi-happy.

try overriding your DNS to your ISP's DNS server address and see if that works.