Router setup

Hi all

Problem setting up the router

I have a windows 2003 server which acts as DHCP server my tcp/ip is as follows
192.168.1.5    ip
255.255.255.0  subnet
192.168.1.5   Gateway

192.168.1.5      DNS

My vpn

Lan

192.168.1.4     ip
255.255.255.0 subnet
192.168.1.5   Gateway

192.168.1.5      DNS    

Wan

10.10.10.2  ip
255.0.0.0    Subnet
10.10.10.1  Gateway

192.168.1.5  DNS

Asuming this is ok

The default gateway I think should be setup on the router but not sure where it’s a small netgear router  and I don’t know if there is any other settings I should apply
Just say if you need more info
Thanks davy


LVL 6
davy999Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

masnrockCommented:
The problem is you have the default gateway all wrong. It should be the IP address of the router, not the DHCP server.

Routers pass network traffic along from router to router across the internet... you have things set up to pass traffic to your DHCP server, which will then try to pass traffic on to itself.

Assuming that all of your machines you've mentioned are behind a netgeat router that has the WAN info you provided as its "public" IP address amd 192.168.1.1 as its private IP, you need to fix the configuration of each machine.

Windows 2003 server should be this:
192.168.1.5    ip
255.255.255.0  subnet
192.168.1.1   Gateway

Lan

192.168.1.4     ip
255.255.255.0 subnet
192.168.1.1   Gateway

I have to ask why you're doing NAT on the Netgear, since that seems to be the case... from what I see, you're doing private IP addressing anyway. Unless you don't want anything outside of that particular router to be able to see anything.

Just let us know what exactly you're trying to do and clarify what the configuration is.
0
davy999Author Commented:
ok

I have a vpn 2003 server with 2 nic's( wan) lets say 10.10.10.2 and (lan)  192.168.0.2
the wan nic is  connected to the router and the lan nic is connected to the switch
which is connected to the lan win 2003 server ad, dns, dhcp,

so my wan should be 10.10.10.2 ip
255.0.0.0 subnet
192.168.1.1 gateway
0
masnrockCommented:
The heck? VPN server has two NICs, that's cool.

WAN information you initially had is right, assuming that's what the network mask and IP for the router is (even though it doesn't quite sound right to me).

It looks like the VPN is supposed to do NAT, and the DHCP server is sitting on the LAN. So if anything, the LAN card in the VPN server should NOT have a gateway address set. However, the DHCP server should be using the VPN server's LAN IP as the gateway. The DNS address probably shouldn't be the DHCP server unless you have DNS running on it... otherwise, it would probably be the same as the gateway as well.

Hopefully, you've made sure to bridge the connections or do something like ICS (can't remember the exact name off the top for Server 2003).

What's the role of the Netgear router anyway?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

davy999Author Commented:
Thank you for your time.

just so i understand a it a little better

1 router

2 subnets

192.168.1.2
192.168.0.2

my router is by default is configured to 192.168.1.1 and gateway 192.168.1.1

Question how do i get the 192.168.0.2 through my router

is it like this 192.168.0.2 ip
                  192.168.1.1 gateway



0
masnrockCommented:
You can do one of two things...
1) Have a router with multiple interfaces with your subnets defined
2) Have a big subnet that 192.168.0.2 and 192.168.1.2 fall under.

I'm assuming your router is the Netgear, which shouldn't let you do what you're trying to do. Problem is that with 192.168.0.2, you're using an address that isn't in the same subnet. So it's not going to know how to route traffic, especially incoming traffic.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
davy999Author Commented:
ok that explains it thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Protocols

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.