Jump to content

vlamnire

Member
  • Posts

    21
  • Joined

  • Last visited

Reputation Activity

  1. Agree
    vlamnire got a reaction from leadeater in Access 192.168.11.x on my 192.168.0.x network   
    If you have the entire network on one router and do not have a special addressing scheme.  Set up your DHCP server with your IP you have now 192.168.0.0 network with subnet mask of 255.255.0.0 which will create a network from 192.168.0.0 to 192.168.255.255 (65,534 hosts allowed on that network) This will make the printer and everything connected on the same network.  Quick and easy until you get your codes then change it back to 255.255.255.0.
     
    I'm a newer networking student studying Cisco equipment so that's my take.
  2. Agree
    vlamnire reacted to KuJoe in Access 192.168.11.x on my 192.168.0.x network   
    Static IPs on devices are always a bad idea IMO. All static assignments should be handled on the DHCP server.
     
    That being said, you can either change your own device's IP address, like others have said, or I believe you can change the subnet for your PC from 255.255.255.0 to 255.255.0.0 and you should be able to talk to it.
  3. Agree
    vlamnire reacted to Howlingwolf101 in Networking NOob Guide   
    Comptia has some books that you can even get certified with, these are college type books though so they're pretty dry. I would check out Networking + 
  4. Agree
    vlamnire got a reaction from Howlingwolf101 in Networking NOob Guide   
    You NEED your certifications or it's going to be hard.  Top industry one's are CCNA and CCNP for Cisco proprietary stuff.  None Cisco certs are JNCIE-ENT, CompTIA Network+ (mentioned by Howlingwolf101), and WCNA.  Many large businesses use Cisco equipment only such as hospitals.  Do you plan to go to school in the future or not?
  5. Informative
    vlamnire got a reaction from dmegatool in Access 192.168.11.x on my 192.168.0.x network   
    If you have the entire network on one router and do not have a special addressing scheme.  Set up your DHCP server with your IP you have now 192.168.0.0 network with subnet mask of 255.255.0.0 which will create a network from 192.168.0.0 to 192.168.255.255 (65,534 hosts allowed on that network) This will make the printer and everything connected on the same network.  Quick and easy until you get your codes then change it back to 255.255.255.0.
     
    I'm a newer networking student studying Cisco equipment so that's my take.
  6. Like
    vlamnire got a reaction from Peter Smyth in Small Home Private Network Setup   
    From a ICT student with a networking systems and design minor try first changing the username and password to remote into the router (don't leave it as admin/password) and set a custom SSID, set it to not broadcast (optional but remember this hides it from the list of anyone searching for a wireless network so you have to manually enter the SSID in whatever device you're connecting with), set the password to a secure one that's WPA2, disable WPS button/function if it has one -- on some routers there is a security risk where a brute-force attack can break the code and connect, if you want to and if it allows you to set up a MAC address whitelist or MAC address filter to only allow the MAC address of your devices to connect so even if someone does somehow get in if they don't have the right MAC address they cannot do anything.  Downside of MAC address filtering is when you get a new device you have to add it to the list via another device before connecting. 
     
    Miscellaneous things can include disabling remote management via browser, SSH and Telnet, so it won't allow outside IP addresses to try and connect, turn on your router firewall and review those settings.  If you want ultimate control try seeing if there is an alternative firmware for your router like DD-WRT.
     
    For a common evil-doer out there a complex password to connect is sufficient.
  7. Like
    vlamnire reacted to MeshFile in How to diagnose network issues?   
    Some clarifications:
    It's the speedtest.net test and it's the problem getting the packet loss results (not 'package loss') because of java? When you say you need to reset the whole network, you mean actually resetting the routers to factory default and not just rebooting them? When the issue where you need to 'reset the whole network' happens, what happened to the test on using your desktop computer directly wired to the modem? It's not getting online? To observe packet loss, use a ping to google.com using (or other servers) using command 'ping google.com -t' and see if it has timeouts whenever your issue occurs.
×