Router config problem

[chunky28]

I am currently attempting to configure my router.

I think I'm almost there but not quite.

I have been assigned a range of IP addresses by my ISP.

However I have been informed that my Netgear Router must be configured with private addresses on my LAN.

At the moment I have the following:

Router

Ethernet:
IP address: 192.168.0.1
Subnet: 255.255.255.0

Remote Note Configuration:
Remote IP address: 0.0.0.0 (not sure if I need to enter anything in here)
Remote Subnet Mask: 255.255.255.240 (supplied by my ISP)
My WAN address: 193.195.xxx.225 (supplied by my ISP)

Single User: Active (to enable NAT)
Default Server: 192.168.0.2 (I have a local DNS setup on this PC with forwarder DNS servers hosted by my ISP)

Each PC has been assigned a private IP address in the default netgear range 192.168.0.2/32 with the gateway set to my Router IP i.e. 192.168.0.1 and a DNS server set to the Microsoft 2000 server machine (192.168.0.2) which as I said has DNS forwarder addresses hosted by my ISP.

If I do a loopback test and ISP connection test on my Router it succeeds but I can't access the internet.

Any help will be most appreciated.

Thanks

Charlie

 

[pansophic]

I hope that you didn't actually use 192.168.0.2/32, as that means that you are the only machine on the network. I belive that you wanted 192.168.0.2/24, which is a Class C netmask (254 hosts).

I still don't understand which of the settings that you describe apply to which device on the network, but if you actually assigned that netmask, it is certainly a problem.


pansophic

 

[chunky28]

When I say 192.168.0.2/32 I basically mean the router will support 32 PC's on the network....ranging from 192.168.0.2 through to 192.169.0.32. (all hidden private IP addresses)

The following are settings in my router GUI:
#####################################
Router

Ethernet Menu:
IP address: 192.168.0.1
Subnet: 255.255.255.0

Remote Note Configuration Menu:
Remote IP address: 0.0.0.0 (not sure if I need to enter anything in here)
Remote Subnet Mask: 255.255.255.240 (supplied by my ISP)
My WAN address: 193.195.xxx.225 (supplied by my ISP)
#########################################################

The way I understand it
....the ethernet menu is used to identify the router to the PC's on my private network. Each PC on the network will have IP addresses in the range 192.168.0.2 through to 192.168.0.34 (although I only have about 14). Each PC will also have a subnet the same as the router.
....the remote node configuration menu is used to identify my router publicly....using a fixed IP address and subnet supplied by my ISP.

I then want to use NAT so external http and smtp requests are routed to the correct private IP address on my network.

For interent use I have a dns server set up on a machine on my private network with forwarder dns servers so each PC can browse the internet using my ISP dns servers.

I hope this explains what I am trying to do and how I have attempted to configure the network and router.....as I mentioned previously though..it isn't working as I can't browse the web.

Please could someone help.

Thanks

Charlie

 

[bcastner]

Say a little more about your local DNS Server. What OS is it? How are the forwarding entries made?

For a local workstation client, could you print out the current ipconfig /all results here?

 

[gconnect]

ok, as far as your internal net you are referencing
192.168.0.0 / 26 (26-bit mask give you 62 available host of which you are using 32

for testing if your router has reachability to the Internet try pinging through it from one of your LAN pc's to an IP address out here on the Internet somewhere: as far as who to ping, you will have better luck initially pinging someone in your ISP's alloted IP range/pool for customers such as yourself. (i.e.- 193.195.xxx.226 , 227, and so forth)Then if that is successful then ping an fully qualified domain-name such as

http://www.yahoo.com

and see if dns resolves it.

i.e.
Start --> Run
type 'command' if Windows 9x, ME
type 'cmd' if NT (2000, or XP)

C:\ping 193.195.xxx.226
and see if you get replies, if you get 'request time out than it's your router.

if successful, then next
C:\ping

http://www.yahoo.com

and see if you get replies, if you get 'request time out than it's your dns setup.


that way you:

1
rule out your side, and your NAT config first

2
rule out DNS

p.s. what type of in-house dns server are you using?

 

[chunky28]

Thanks gconnect.

I will try the tests when I get to work on Monday morning.

I have just set up a dns server when I installed Windows 2000 Advanced Server (sp3). This won't resolve anything other than internal hosts. As part of the DNS configuration I supplied two forwarder dns servers supplied by my ISP.

If there is any other info that might help someone suggest what the problem is please let me know.

Thanks

Charlie

 

[bcastner]

Two things to watch out for:

1. That the router firewall, or client firewall, is not blocking DNS queries to your internal server. DNS uses UDP and TCP port 53. The DNS Service Management console also uses remote procedure call (RPC). RPC uses port 135. These are potential issues that could arise when you configure DNS and firewalls.

2. That in creating the DNS server you removed any root zone definitions. On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints' tabs because they are greyed out, that is because there is a root zone (".&quot present on the DNS server. You MUST delete this root zone to permit the server to forward unresolved queries to yout ISP or the root servers. Accept any nags etc, and let it delete any corresponding reverse lookuop zones if it asks.

 

[chunky28]

Thanks bcastner.

I have just called Netgear and now they are saying I can use my public IP addresses! I wish they would make their mind up.

This is how I had my network and router configured previously. When setup this way I can access the web from any PC.

The problem I am now having is enabling access to my website hosted at an IP address on my LAN. I have the domain name registered to my Router IP and I am trying to use NAT to forward requests to the correct IP on my LAN.

I have not had any success yet but I'm looking into it.

The Internet Access setup menu for my router has the menu items:
-Single User Account
-IP address

I have been told by Netgear I must set Single User account to Yes and the IP address to 0.0.0.0.....This should enable NAT.

Then I believe I need to configure routing using the SUA Server setup menu, so port 80 requests are routed to the IP address at which my website is hosted.

No joy yet though!

I think the router might be faulty....Netgear are sending me a new one to try out.

Thanks again to you all

Charlie

 

[chunky28]

Fixed the problem! Thanks to all for your suggestions.

Cheers

Charlie