workstations have no internet access, restart ras and routing and it works please help

S

somethingverycool

Hey everyone

my problem is as follows and hope someone can help

server is running server 2003, 2 nics, 1 to router 1 to internal
network.

Nearly everyday we cannot access the internet and the only way we can
fix this problem is to either restart the server or restart ras and
routing.

There are no errors in the application or services event log.

The server can access the net no worries, however we cannot vpn into
the server either.

Anyone got any ideas of what the problem could be.

Thanks in advance
 
K

Kurt

Hey everyone

my problem is as follows and hope someone can help

server is running server 2003, 2 nics, 1 to router 1 to internal
network.

Nearly everyday we cannot access the internet and the only way we can
fix this problem is to either restart the server or restart ras and
routing.

There are no errors in the application or services event log.

The server can access the net no worries, however we cannot vpn into
the server either.

Anyone got any ideas of what the problem could be.

Thanks in advance
Click to expand...
On common mistake when configuring RRAS for NAT is to supply a default
gateway on the server's LAN interface. Make sure you only have a default
gateway set on the public interface. Also, do a route print and see
where the 0.0.0.0 entry is going when it is working and when it is not
working.

....kurt
 
S

somethingverycool

Hi Kurt

thank you for the reply

do I change the default gateway settings under rras or under the
network interface?

also here is a copy of the route print can you advise if you see any
problems

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x10003 ...00 02 b3 e7 b5 a6 ...... Intel(R) PRO/100 S Desktop Adapter
0x10004 ...00 30 48 87 47 0d ...... Intel(R) PRO/1000 PL Network
Connection
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.1
20
0.0.0.0 0.0.0.0 192.168.16.2 192.168.16.2
20
58.171.90.61 255.255.255.255 192.168.0.254 192.168.0.1
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1
20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1
20
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2
20
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.16.26 255.255.255.255 192.168.16.29 192.168.16.29
1
192.168.16.29 255.255.255.255 127.0.0.1 127.0.0.1
50
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2
20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1
20
224.0.0.0 240.0.0.0 192.168.16.2 192.168.16.2
20
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1
1
255.255.255.255 255.255.255.255 192.168.16.2 192.168.16.2
1
Default Gateway: 192.168.0.254
===========================================================================
Persistent Routes:
None

thank you in advance :)
 
K

Kurt

Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.1
20
0.0.0.0 0.0.0.0 192.168.16.2 192.168.16.2
20
58.171.90.61 255.255.255.255 192.168.0.254 192.168.0.1
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1
20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1
20
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2
20
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.16.26 255.255.255.255 192.168.16.29 192.168.16.29
1
192.168.16.29 255.255.255.255 127.0.0.1 127.0.0.1
50
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2
20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1
20
224.0.0.0 240.0.0.0 192.168.16.2 192.168.16.2
20
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1
1
255.255.255.255 255.255.255.255 192.168.16.2 192.168.16.2
1
Default Gateway: 192.168.0.254
===========================================================================
Click to expand...

Notice you have two default routes:

0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.1
0.0.0.0 0.0.0.0 192.168.16.2 192.168.16.2

This can be a problem. One says your default gateway is 192.168.0.254
and the other is 192.168.16.2. You should only have one default route.
If you need both routers (one for Internet and one for internal routing)
and you can't set the routing up on the routers themselves, instead of
two default routes, you should manually add specific routes that need to
go through the internal router. If you don't use both routers, you
should remove the unused one, usually from TCP/IP properties. If the
192.168.16.2 is the VPN adapter IP, you may need to make changes in
RRAS. Either way, it seems that 192.168.16.2 is a local IP address on
the server and probably can't function as it's own gateway. The only
time you should have two default gateways is of both are accessible, and
then you should define metrics so the preferred route is used first.

....kurt
 
S

somethingverycool

Kurt said:
Notice you have two default routes:

0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.1
0.0.0.0 0.0.0.0 192.168.16.2 192.168.16.2

This can be a problem. One says your default gateway is 192.168.0.254
and the other is 192.168.16.2. You should only have one default route.
If you need both routers (one for Internet and one for internal routing)
and you can't set the routing up on the routers themselves, instead of
two default routes, you should manually add specific routes that need to
go through the internal router. If you don't use both routers, you
should remove the unused one, usually from TCP/IP properties. If the
192.168.16.2 is the VPN adapter IP, you may need to make changes in
RRAS. Either way, it seems that 192.168.16.2 is a local IP address on
the server and probably can't function as it's own gateway. The only
time you should have two default gateways is of both are accessible, and
then you should define metrics so the preferred route is used first.

...kurt
Click to expand...

Thanks a heap for your advice thus far Kurt

this is what my route table looks like now is that correct

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 02 b3 e7 b5 a6 ...... Intel(R) PRO/100 S Desktop Adapter
0x10004 ...00 30 48 87 47 0d ...... Intel(R) PRO/1000 PL Network
Connection
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.1
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1
20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1
20
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2
20
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2
20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1
20
224.0.0.0 240.0.0.0 192.168.16.2 192.168.16.2
20
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1
1
255.255.255.255 255.255.255.255 192.168.16.2 192.168.16.2
1
Default Gateway: 192.168.0.254
===========================================================================
Persistent Routes:
None

cheers
 
K

Kurt

Thanks a heap for your advice thus far Kurt

this is what my route table looks like now is that correct

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 02 b3 e7 b5 a6 ...... Intel(R) PRO/100 S Desktop Adapter
0x10004 ...00 30 48 87 47 0d ...... Intel(R) PRO/1000 PL Network
Connection
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.1
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1
20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1
20
192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2
20
192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2
20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1
20
224.0.0.0 240.0.0.0 192.168.16.2 192.168.16.2
20
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1
1
255.255.255.255 255.255.255.255 192.168.16.2 192.168.16.2
1
Default Gateway: 192.168.0.254
===========================================================================
Persistent Routes:
None

cheers
Click to expand...

Looks OK. At least there's only one default route. Does everything work
now? What did you do to fix it?

....kurt
 
S

somethingverycool

Hi Kurt

Thank you for all your help all things seem to working well so far.

Much appreciated for all your help :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

VPN RAS link speed slow and/or fluctuates 0
Server 2008 RAS Only allowing clients to see local subnet 0
Simple RAS Routing? 2
Deny users web access on RAS router 3
RAS setup - routing 1
W2003 SP1 RRAS: wrong routing table entry after client VPN connection 3
RAS, Lan Routing, and Demand-dial routing. 1
Does RAS log IP Address Pool Assignments to usernames and where??? 0

Top