Tech Support Guy banner
Status
Not open for further replies.

Windows 2003 Server Routing Issue

704 views 0 replies 1 participant last post by  dangermouse1977 
#1 ·
Hi all, my first time on this forum, so I'll try and post as much information as I can in the hope that someone can help me out.

I have a Windows 2003 server with 2 nics in.
NIC1 is connected to the office hub

NIC1 IP 192.168.1.100
sn 255.255.255.0
dg 192.168.1.1
dns 10.0.0.2 and 192.202.252.240

NIC2 is connected to a Linksys RV042 load balancing Internet Router

NIC2 IP 192.168.1.102
sn 255.255.255.0
dg 192.168.1.1
dns 10.0.0.2 and 192.202.252.240

Linksys RV042 router

LAN IP 192.168.1.1
WAN 1 IP (cable modem) 41.205.46.171
WAN2 IP (ADSL modem) currently disconnected

All workstations have static IP addresses in the 192.168.1.* range with 255.255.255.0 s/net and 192.168.1.100 default gateway

My problem is that we appear to have some kind of routing issue in that often the internet doesn't work on the workstations, although it will remain working on the server.
Also certain PCs resolve the name of the server to the 192.168.1.102 IP address when you try and ping the server by name - the pings are not returned.

Within the routing and remote access section of the server there are a couple of routes defined under network interfaces, general, IGMP and NAT.
These routes are either entitled router or hub, the router ones use the .102 address with a gateway of 192.168.1.1 and the hub ones use the .100 address with a 1.1 gateway.

Anyone care to offer suggestions as to what's wrong with my network and what I should do to sort it.
It should be noted that due to the type of environment that I am in, I am forced to undertake any changes in a live office situation - I can do nothing after hours.

Thanks in advance, any more information needed, please ask.
 
See less See more
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top