Windows 10: PC not picking up wirelessly from router

My pc is not linking wirelessly to the router. I have read all the forum responses to this particular problem and none work. I can’t help but feel it’s something simple and I’m missing it. I have spent hours on this and if I don’t get it sorted then it’s Beachy Head for me

:)

 

How to configure a wireless router and an ADSL router to provide an internet connection

I made a mistake when purchasing a faster wireless router and did not specify it should have an ADSL port. So to use it I have connected it's WAN port to a LAN port of the ADSL router.

There seem to be several ways of configuring these devices. Could someone suggest the "best" or "most beneficial" way please?

There are 2 PCs and one printer connecting wirelessly.

One of the PCs picks up a dynamic IP

The other PC has a static IP (192.168.0.200)

The printer has a static IP (192.168.0.210)

Wireless router

• Lan IP: 192.18.0.1
• WAN IP: 10.0.0.248 (static)
• WAN default gateway: 10.0.0.2

The ADSL router connects to the internet fine. I have turned off dynamic IP.

The PCs connect to the wireless router, the internet and each other ok.

The printer connects and works if set to use the ADSL router's default gateway (10.0.0.2) and a static IP (10.0.0.251). It connects but does not work if using the wireless router's default gateway (192.168.0.1) with a static IP (192.168.0.210)

I would like the printer to connect the wireless router and work...

I don't know why I selected DNS IPs. The primary is 062.024.134.005 on the PCs and wireless router. I get the impression this is a separate issue from the connections problem above.

 

How to factory reset Cisco 1700 Router

Hopefully I can help you here....its a very common thing to happen.


First, I take it you dont know the passwords for console access or telnet/ssh?

I will assume that these devices belong to you.

step 1. Plug a cisco console cable into a serial port on your pc
step 2. Plug other end into Cisco console port
step 3. Using hyperterm or putty or similar connect to the serial port
step 4. boot router, and make sure you clearly can see the output (this confirms you have good serial comms)
step 5. if this fails, adjust the comm port settings (9600, 8,1,n are the default)
step 6. now you have to do the only hard part...send the break command:

Break command list: Break Commands

Go down the list and match your OS and SW and try the sequence suggested.

If this fails several times do what I do: Install putty (free) and then to send a break so you can get into rommom just hit "ctrl-a b".

 

router logs DoS attack from a local PC....

Well you did not say that you don't really know what you are doing. It's not a problem of course, but it changes things a little.

It's not even clear if the PC or the router is the problem at this time, so I suggested that you disable some unnecessary things which are usually known to cause many problems, sorry if those were too complicated.

• You could reset some network related stuffz on the PC as a next step. Open an elevated command prompt (run as administrator), and enter the followings on the PC:
  netsh int ip reset reset.log
  netsh int ipv6 reset
  netsh winsock reset
  netsh branchcache reset
  netsh advfirewall reset
  (note: You can export your current firewall rules in the "group policy" before the reset if it's needed for some reason)
  
  
• Btw, Would it be a problem to reset the router to the default settings if the things we are trying will not help? There is a menu point for that called "factory settings" (and also a little hole on the back if you prefer that one).. the Administrator username in the router after the reset would be admin and the password is probably on a sticker at the bottom of the router (special settings needed to go online with your ISP might be also necessary)
  This is not needed now (not yet), but perhaps the source of the problem is at the router and not the PC in question, so we may come to that eventually.

ps.: Do you have a second network card you could test in that PC and a different cable to rule out some hardware issues on the PC side?