atcomsystems.ca/forum Forums VOIP Phones & IP PBX Networking static ip issue

hey guys.
I got the BELL fibe installed in my house,my issue is that if i put a pc with a static ip,it wont let me connect to the internet,internaly is fine.i think its the bell modem blocking something,any ideas?

Look at your router's firewall settings and check to see if static IP is blocked. Also, make sure your static IP is in the same subnet as your gateway which is usually the router.

Rcaman

can you post the IP address of your modem/gateway and the static IP you're trying to use?

modem is 192.168.2.1
i set dhcp from 192.168.2.10 to 192.168.2.20

i have my pc set to 192.168.2.199
i don't see any firewall settings in this modem

i called tech support and they don't support static ip,
i think its the modem bloking it,should i just get a dlink router instead??

I'm not familiar with how the FiOS works in Canada. You should call the provider and ask them which router will work on their system AND support static IP.

Another way to go is disable the routing and DHCP in the router and set up a DHCP server. That way, no matter what the address is on the server side, you will have access to the internet.

Rcaman

The modem really shouldn't be able to tell if the traffic coming through it is from a static or dynamic IP .... it should just route the traffic.

What is the subnet mask?

As far as the D-Link router the answer is yes .... set it to get an IP from the ISP and then you can set the inside up to do dhcp from 10-20 like you have and any of the others could be used for statics.

subnet is 255.255.255.0

A run of the mill router isn't going to "care" if an address has been configured via DHCP or Static. Yes, in extreme cases of security requirements, access can be locked down via IP address or MAC address on a LAN but a SP is not going to go to that trouble on a home/office install. They wouldn't know what to program.

I would suggest breaking this down into pieces...

Your PC is 192.168.2.199/255.255.255.0 and the router is 192.168.2.1/255.255.255.0

If this is a windows PC open a command window (hot key is Windows + "R", type "cmd", then enter and a DOS style screen will open).

Now you will ping some things. From the command window you are going to type ping space then the values given below.

I apologize if you already know this but in my tech support calls it happens often enough that I do ask.

From a command window can you ping 192.168.2.1 and get replies? As long as the patch cable, NIC card and switch port are good you should get a reply. This will prove connectivity physically and logically to the router.

Now try and ping 4.2.2.2 or 8.8.8.8 If you get a reply this will prove you have access to the internet since these are high level DNS servers.

Now try and ping Google.com You might get an error to the effect that the name could not be resolved. If you get this check the DNS setting on your NIC. It might still be configured to obtain automatically which won't happen since you are no longer using DHCP. Try assigning your router address, submit, and test. If still not working then from a workstation that pulled an address using DHCP run ipconfig /all. Detailed information about all the network interfaces will be presented. Look for what IP addresses have been assigned for DNS (usually there are 2) and plug these values into the DNS for your static staion and test again.

If you can ping google.com then you are good to go. You will even see the actual IP address of google.com using this command.

What I suspect is happening is that DHCP is providing all the information needed (IP address, gateway, mask, DNS) and that DNS info has not been configured on the static machine. I have had experienced technicians forget this and then call me. I say "DNS?" and you can "hear" the cheeks flushing.

I hope this helps you out. ~ Mike

i can ping my router no problem and any other devices like my dvr is 192.168.2.199.
i tried 4.2.2.2 or google.com i get transmit failed general failure

Mike makes some good points.

Go to the PC, open a DOS window and type ipconfig /all

Write down the IPv4 address, the gateway IP address, the subnet, the DNS IP Address and the status of NetBIOS over TCP/IP.

With that info, we can make some educated guesses.

Rcaman

if i set my pc to dhcp i can go to the internet no problem

See RCAman's post. That'll give info needed to help.

When you set your static address, are you also setting the DNS Server addresses? Set the first one to the same as your gateway and see what happens.

I'm going to reiterate what RCAMAN already said.

On Windows, you can run ipconfig /all to get all of your network settings quickly through command prompt.

Start > Run > cmd

Make sure that the address you're assigning to your computer is in the same subnet as your router.

Example:

Router: 192.168.2.1
Subnet Mask: 255.255.255.0

PC #1: 192.168.2.199
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.1 (this points any requests from your PC to the router)
DNS Server 1: 8.8.8.8 (for testing purposes you can use OpenDNS, but these settings are usually assigned automatically using DHCP)

If you want to keep the same IP address on your PC all the time, and don't want to mess with having to manually set everything up, consider setting a DHCP reservation on your router. I can help you with this, I would just need to know which brand and model you have so I know how to walk you through the configuration page.

This setting will keep the same IP address assigned to the MAC address (basically a serial number for your network/Wi-Fi card) associated with your machine, every time you log onto the network.

Hope this helps.

Scott

Man you guy's rock.
i put in my modem ip/router 192.168.2.1 and in dns server,
not it works,
I'm finally trying to figure out networking i always subed that out.
Thanks for helping a IT Newb

Wait one second!!!

You said your PC was set to 192.168.2.199 and now your saying your DVR is also set to that address.

You can't have the same address assigned to two different location

sorry pc was at 198

Sentrex - Congratulations! Kudos to you for wanting to learn more. Once you have the basic concepts down, you will be a pro in no time.

You learned a lot of basic troubleshooting today.

For now these commands are your friends and will always be your friends...

ping - If you get a reply that is good. Start by pinging the router. If no reply then that must be fixed.

DNS - Very easily missed/forgotten. Ping can help you discover this. You can always try and ping 8.8.8.8 or 4.2.2.2 to test internet connectivity. If you can ping the 8.8.8.8 but not Google.com then check DNS settings on the station.

Tracert - Tracert google.com You will see the path your packet take to google.

Ask, ask, ask. We have all been where you are and will be glad to help.

A Network Plus class and certification might also be helpful. It really helped to get me started and built my confidence. ~ Mike

Sentrex - I love to teach so here is what is going on with your setup on a high level now that it is working...

Your network has a network address (aka a wire address) of 192.168.2.0 The subnet mask of 255.255.255.0 determines this. Each digit of an IP address is called an Octet and is based on a 8 bit number. It can have a value of between 0 and 255. The subnet mask determines what part of an address is the network and what part is the host (PCs, printers, servers, router etc...) For now, since you are learning, the 255 masked the entire number so the network above is 192.168.2.XXX

The last octet is reserved for hosts. As explained above, it can be any value between 0 and 255. This would lead you to think you can have 256 devices right? Wrong! 0 is reserved as the network address (think of this as the network ID) and 255 is a special address that sends information to all devices on a network (1-254). So we now have 1-254 available to assign to devices meaning we can have 254 devices on this LAN.

Every device must be assigned an IP address of 192.168.2.(something between 1 and 254) in order to communicate with other devices. The last digit must be unique. You cannot have 2 devices with 192.168.2.200 or you have created an IP address conflict. What will likely happen is one of the devices NIC cards will shut down until you fix this. If you assign a workstation the same address as your router though, you might kill your internet until you find it.

Your devices connect to a LAN switch. The switch has a table that maps the MAC address (a unique 12 digit address assigned to every device out there) with the IP address assigned by you or the DHCP server.

DHCP vs. static - For workstations, DHCP makes management easier. Your router can be configured to assign addresses to stations automatically so you don't run into the adventure you had today. That being said, sometimes a static address is needed for an email server or surveillance and (definitely) the router.

When you assign a static address you need 4 components. An IP address and Subnet mask as explained above. The default gateway will be the address you router has (192.168.2.1). Lastly you will need a DNS server assigned (also 192.168.2.1) As you saw, once these were configured it worked.

So here is what is going on. Internal vs. outside...

When I ping my DVR (192.168.2.199) from my PC (.198) the PC sends out a special packet that will be replied to from the other side if it is received. The switch knows where .199 is and sends the packet to the DVR. The DVR responds with a reply back to .198 which the switch, again, knows how to get to.

If I ping 8.8.8.8 the computer already knows this is in a different network so it will send the request to the router (.1) to find it. If no default gateway is configured (or incorrectly configured) the process will fail.

Your router is a device that connects 2 or more networks together (in this case your 192.168.2.0 network and the Internet)

If it can get to the router and the router can find 8.8.8.8 on the internet you will get a reply back.

Now we are good with IP addresses. So I ping google.com and get a result that the hostname could not resolve. There are special servers on the internet that maintain databases of which IP address is associated with which human friendly name such as google.com Google.com might be IP 74.68.7.190 but no one is going to remember that so we have DNS servers out there to resolve names to IP addresses. You router by itself is not a DNS server but it did a DHCP to your service provider to get an IP address, subnet mask, default gateway and DNS servers (sound familiar now?) from the SP network. If you google search "What is my IP?" you will see the external IP address to your network. Your firewall will (hopefully) keep out all traffic except for that you allow in.

This is a good base to build on - It does get more interesting when you learn about more complex subnetting, routing, and other concepts but as far as simple LAN setups you have really accomplished a lot today. Before you know it neighbors, family, and friends will consider you there go to guy. ~ Mike

In closing from a cmd line type tracert google.com and you will see the path the packet takes. Basically it is router to router to router until it gets to google. There are webpages that will even graphically show the path on a world map.

its a BELL sagemcom fast 4350 home hub 1000

wow thanks michael that puts it in a way that i now understand

Just want to tack on one quick addition to Michael Meyer's excellent lowdown.

For local area networks (versus WAN/Wide Area Networks), there are three ranges of IP addresses normally used for internally assigned IP addresses.

10.X.X.X
192.X.X.X
172.X.X.X (this is the least commonly used one)

These addresses aren't used outside of Local Area Networks, because this would cause a conflict, as your router wouldn't be able to distinguish between local traffic and requests for content outside your network.

Here's an example of a traceroute to Google.com, like Mike mentioned:


--------------------------------------------------------





Hope that helps.

Scott

You guy's have made me so happy,my network works my ip office with ip sets works i can go on the internet and i understand now the basics,
I hope i can help you guy's out in the future
Alain

Just to clarify, the RFC 1918 private IP ranges go like this:
10.0.0.0-10.255.255.255
172.16.0.0-172.31.255.255
192.168.0.0-192.168.255.255

https://en.wikipedia.org/wiki/Private_network