Link to home
Start Free TrialLog in
Avatar of i2o
i2oFlag for South Africa

asked on

Mixing IP addresses over 2 x NIC's

I have just taken over a Server 2008 Std that currently has 2 NIC's configured as:

#1
Description: HP NC362i Integrated DP Gigabit Server Adapter
Physical Address: 78-E7-D1-F5-A9-B0
DHCP Enabled: No
IPv4 IP Address: 10.26.213.130
IPv4 Subnet Mask: 255.255.255.240
IPv4 Default Gateway: 10.26.213.129
IPv4 DNS Servers: 196.43.6.30, 196.43.42.190
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
Link-local IPv6 Address: fe80::942b:af7c:c15b:3262%10
IPv6 Default Gateway:
IPv6 DNS Server:

#2
Connection-specific DNS Suffix:
Description: HP NC362i Integrated DP Gigabit Server Adapter #2
Physical Address: 78-E7-D1-F5-A9-B1
DHCP Enabled: No
IPv4 IP Address: 192.168.4.1
IPv4 Subnet Mask: 255.255.255.0
IPv4 Default Gateway:
IPv4 DNS Server:
IPv4 WINS Server: 192.168.4.1
NetBIOS over Tcpip Enabled: Yes
Link-local IPv6 Address: fe80::695f:4132:705c:c0bc%11
IPv6 Default Gateway:
IPv6 DNS Server:

Now I am aware that having the NIC's with different addresses is not really a good idea. Especially with DHCP on the server enabled and DNS.

However the #1 NIC connects via a VSAT link with a set IP Address  10.26.213.129.

The problem I am currently having is that users cannot access the Internet but you can direct from the Server.  

Any suggestions on improving / resolving this situation?
     
SOLUTION
Avatar of Leon Fester
Leon Fester
Flag of South Africa image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of i2o

ASKER

The PC's are currently set as 192.168.4.34, 255.255.255.0, Gateway 192.168.4.1, DNS 192.168.4.1
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of i2o

ASKER

Sorry for the delay in getting back to you been at the coal face so too speak.

Ok, your comments are fully justified and taken into account for further setup. However I have resolved the issue by disabling the RRAS and then enabling it and as you know you then have to re set it up. Did this and hey presto all the routes are correct and the users now have access to the Internet. It would seem that a previous tech had loaded Endpoint on the Server and this is where the problem originated. What Endpoint did to the RRAS, I do not know. But it was 'fixed' by doing the above.

Thank you for your comments and I will take them into account when we set this up correctly.

Regards
Avatar of i2o

ASKER

The error was resolved by reloading the RRAS.