Peer to peer not accessing internet

[dale@fcg]

Linksys router acting as dhcp, Verizon DSL, 2 XP pc's that can see each other fine but neither can access the internet via the router. Internet is fine direct to a PC. Put the Verizon pw and user id below the PPPoE box in router interface.

When I checked the PC's IP address (set to obtain ip automatically), I noticed that the DNS server was same as the Gateway (192.168.x.x). Shouldn't the DNS server be something unique supplied by the DSL modem (via Verizon server)? Also, would that be static or would Verizon change the DNS server number every so often? If static, could I use the DNS number of another DSL connection within that neighborhood? Can I use static IP for machines connecting to Verizon DSL?

Am I onto something that the router (dhcp) is not assigning the correct DNS server?

[Dan18960]

Linksys router acting as dhcp, Verizon DSL, 2 XP pc's that can see each other fine but neither can access the internet via the router. Internet is fine direct to a PC. Put the Verizon pw and user id below the PPPoE box in router interface.

When I checked the PC's IP address (set to obtain ip automatically), I noticed that the DNS server was same as the Gateway (192.168.x.x). Shouldn't the DNS server be something unique supplied by the DSL modem (via Verizon server)? Also, would that be static or would Verizon change the DNS server number every so often? If static, could I use the DNS number of another DSL connection within that neighborhood? Can I use static IP for machines connecting to Verizon DSL?

Am I onto something that the router (dhcp) is not assigning the correct DNS server?

Dale,

While DNS servers do not change often they do occur. Your Linksys router should update the the DNS when required. Now the IP address assigned to your WAN will change from time to time. I have one client that the DSL IP address changes almost weekly while another DSL client has had their's for MONTHS.

Usually what I do is power cycle the modem and the router. Turning off the modem, turning off the router, turning on the modem and letting the LEDs complete configuration BEFORE powering up the router, and after all the lights (except the ethernet) are on I power up the router.

As for assigning static ip addresses to the workstations - you can do that and I have for remote access to my systems via WAN.

[dbarrow]

Dale, are you talking about DNS on the machine? That should be a router address as the machine gets its DNS from the router. Each machine will be assigned an IP number by the router DNS ie: 192.168.0.1 etc.

The router should get (automatic) its' DNS address from the ISP. The Status box in the router config should show the IP of the modem (assigned by the ISP DNS) and the DNS server it uses.

Make sure in configuring the network properties on the machines that you select "This machine connects to the internet through a residential gateway" and not "directly"

[dale@fcg]

Dan,
If I assign static IP, would I just leave lower box of TCP/IP properties sheet set to obtain DNS Server automatically, while setting the IP, Subnet, and Gateway in the upper portion?


Doug,
Where in the network properties do I find the option to go through a residential gateway? Also, if the router's status page shows different (proper) DNS numbers, should I manually (static) configure to those number on the pc's?

Lastly, does Tortanick's post apply here http://www.kickenhardware.net/forum/showthread.php?p=7219#post7219 , perhaps I could use these dns numbers? Where in Linksys router config page would I be likely to find the option to set it statically?

[dbarrow]

IF you run the Network Wizard, that is one of the first options boxes.

IF you set them up manually as static routes, you will need to assign static IPs in your router, ie:
Machine 1 is set as 192.168.0.2 (because the router is 192.68.0.1)
Router static route assignments: Machine 1 192.68.0.2
etc., etc.

In your router configs, there will be an option box somewhere to either obtain DNS from ISP or select another (static) DNS server and an alternate.

[Dan18960]

Dale,

Doug and I DISAGREE on the wizard. It is the LAST thing I would ever run to set up ANY network configuration.

I find that the wizard has hosed MORE peer to peer networks than Carter has Liver Pills.

STATIC configuration:

IP ADDRESS - this is for the local machine - should be OUTSIDE of the router assignments. Linksys assigns 100 - 150 (192.168.1.100 - 192.168.1.150) so I usually start at 155 and increment in sets of 5.

Subnet - 255.255.255.0. This masks ALL but the last number for authentication. This means that a computer that IS NOT using a class of 192.168.1.xxx will NOT connect to your network. BUT any computer with 192.168.1.nnn WILL be "allowed".

Gateway - this is USUALLY the router (it can also be a server that is setup for port forwarding and the Forwarding Zones is not looped to 127.0.0.1) and with Linksys would be 192.168.1.1.

DNS - this is needed for resolving url's to ip addresses. You "should" have the primary DNS as the router since it does forwarding to the ISP / internet provider DNS servers. Also by NOT having a DNS resolving location with static ip addresses it can prevent connection to the internet since the hosts file doesn't know where to send a request to for translating.

In a nut shell, my setups are:

nnn.nnn.nnn.1 - nnn.nnn.nnn.10 is for routers and waps.

nnn.nnn.nnn.25 - nnn.nnn.nnn.49 - Servers / Network appliances.

nnn.nnn.nnn.50 - nnn.nnn.nnn.99 - Printers and print servers.

nnn.nnn.nnn.155 - nnn.nnn.nnn.254 - workstations static assignments.

This way I can trace, track, and diagnost most issues. It also allows for stepping in hardware where I don't have routers between servers or printers between workstations, etc, etc.

I had a recent issue when a printer was put on a network by another company and they didn't setup a static ip address. It caused the workstation/server (which was in place BEFORE I started with the account) to be blocked from the other workstations and nothing would connect and the workstation server would not connect to the internet. I went in and corrected the printing temporarily and told the client to have the printer company come out and "fix" their mistake. Well the company was TOO busy to fix the problem and when the power went out the printer setup a different ip and no one could print. I FIXED the printer and assigned the ip address and now everything is solid.

Moral - IF you want to do a job PLEASE do it RIGHT! ! ! I have little patience for shody work and EVERYONE knows it here :spider: :)

[dale@fcg]

Problem was that the Westell modem was also a router and needed to be turned into a modem bridge by disabling some option within the modem setup page. Linksys led me to this and Verizon's web site detailed how to do it. Problem resolved! Thanks for all the help.

[dale@fcg]

Dan,
My normal configuration for peer to peer is to use the dhcp from the router to assign ip addresses to workstation pc's, and static print servers. My DNS server is always some address way different than the 192.168.1.xxx that the router assigns to the pc's. Of course the gateway is 192.168.1.1
. Right now my dns via dhcp is 71.242.0.12 and 151.197.0.39, which I assume comes from my Verizon DSL modem.

My question is that if I want to set the pc's up as static, do I want to set the dns to 192.168.1.1 ? Will the pc use this dns settting to then go thru router and find modem?

[Dan18960]

Dan,
My normal configuration for peer to peer is to use the dhcp from the router to assign ip addresses to workstation pc's, and static print servers. My DNS server is always some address way different than the 192.168.1.xxx that the router assigns to the pc's. Of course the gateway is 192.168.1.1
. Right now my dns via dhcp is 71.242.0.12 and 151.197.0.39, which I assume comes from my Verizon DSL modem.

My question is that if I want to set the pc's up as static, do I want to set the dns to 192.168.1.1 ? Will the pc use this dns settting to then go thru router and find modem?

I had to read the last paragraph several times BUT the answer is YES. Since the router is acting as a dhcp "server", it will forward any requests not resolved on the network to the ISP resolving DNS servers. The ones listed at the modem/router level.

[Spawn]

This is a dynamic allocation issue.

I have trouble with my NAPT connection also, so don't feel like you're the only one! To be more specific concerning my network, it is NAT that is causing trouble connecting directly to my system. It is damn secure, but if I desire to utilize more advanced networking, I have to pay for it with cash!!!

As far as your question concerning DNS, you should configure a network computer's DNS to the IP of the router. The router will pass the DNS request to the ISP's DNS if configured correctly.

Although, I do not setup my local router in this manner, the logic is sound, and the request should be passed to the ISP.

Vince