Default router and DHCP

I connect to a WiFi router with internal DHCP server. When I set my MacBook Pro to get its address via DHCP, it gets the proper DNS and default gateway addresses, but can't reach the Internet.
If I manually assign an IP address, and enter the same default gateway address as what comes down from DHCP, everything works OK.
How can I get my Internet connection to work properly while using DHCP?

Don't suppose you've got any proxy servers there? All "connected to network" means is that you have a live connection from your Mac to the next hop (could be a an ethernet cable that is connected from your mac to a switch, with the switch connected to nothing else for all your Mac cares!).
Have you actually tested pinging addresses from your PC? That's your positive control. Your firewalls may be set to drop ICMP (ping) traffic. If that's the case, then trying to ping something is not a useful test. Given that you can ping to obtain an IP address from another machine in the office, i'd say you have a DNS issue somewhere too. Confirm that the other machines are not actually using an internal DNS server (it's unlikely they'll use an external DNS server as a primary). What is used at the office? Is it an Microsoft Active Directory site?
There is definitely something different between the DHCP details and the static ones. That is the only way that you can have differing results like that (unless it is not an IP problem but something external to it such as a proxy).

Similar Messages

I´m doing a design for presale, where I will need a router what support PAT for 500 or a little more of users, it not need any more features only static routing and dhcp pool for 500 users, can you help me for know what router recommend?

I´m doing a design for presale, where I will need a router what support PAT for 500 or a little more of users, it not need any more features only static routing and dhcp pool for 500 users, can you help me for know what router recommend?

What is your WAN speed currently and projected WAN speed in the next 3 years?

WRT120N on non-default network and DHCP problem

Hello,
I have setup the WRT120N on my network with an address like 192.168.3.X, the problem is that I cannot setup the DHCP server to serve on this network, it is fixed on the 192.168.1.X.
Is there a way to change this or I really need to setup my network around this router?
Thanks
Ivan

These settings are not possible. You cannot use the same IP subnet on the internet connection and the LAN. Routing happens based on IP addresses and subnet masks. 192.168.3.* addresses are on the WAN and the LAN side. How is the router supposed to know whether it should route an IP like 192.168.3.7 to the WAN side or the LAN side?
Actually the router should not allow you to set up this. Can you press Save settings with these settings and it is accepted? That would be a firmware bug. The LAN address should never be accepted with a internet address you have set.
Your settings suggest you don't want to use the WRT as router but as wireless access point and ethernet switch to extend your existing LAN. If that's the case, the correct setup would be to switch the internet connection type back to Automatic/DHCP. Leave the LAN IP address as it is or set it to 192.168.3.11 if you prefer that.
In addition, disable the DHCP server. (as you have it in your screen shot). The WRT cannot be a DHCP server when used as access point.
Save settings and then wire one of the numbered LAN ports of the WRT to your existing LAN. Don't use the internet port! Now the WRT is a simple wireless access point and ethernet switch. It does not do any routing, DHCP, or similar.

Can you help? Two dialer interfaces with IP SLA for default route failover - issues

I have an issue with a Cisco 2821, it has an ADSL2+ HWIC whose ATM interfaces is linked to dialer 1 and a Gi0/1 interface with a pppoe client which is linked to dialer 2. Both dialer interfaces are up with their respective IP addresses. If the ADSL on dialer 1 fails i want the IP SLA to kick and and replace the default route for dialer 1 with one for dialer 2.
This config works if you manually shut down the dialer 1 interface, it injects the default route for dialer 2 and then when you unshut the interface, the default route for dialer 1 comes back. The problem i have is if you take out the cable for the ATM interface and take it down, it does not take the route out the routing table and the default route for dialer2, which works if you just shut down dialer 1 does not appear.
whats the difference between shutting down dialer1 and it fails over the default route and taking the cable out then it does not?
Here is my config, i'm sure its something simple i'm doing wrong, can anyone help???
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
logging message-counter syslog
enable secret 5 $1$qOOJ$HV5AH6US/YZMuCGPYp3pP.
no aaa new-model
dot11 syslog
ip source-route
ip cef
ip dhcp excluded-address 192.168.0.1
ip dhcp pool pool1
network 192.168.0.0 255.255.255.0
default-router 192.168.0.1
dns-server 188.92.232.50 188.92.232.100
no ip domain lookup
no ipv6 cef
multilink bundle-name authenticated
voice-card 0
no dspfarm
archive
log config
hidekeys
track 1 ip sla 1 reachability
interface GigabitEthernet0/0
description Gi0/30 Local LAN
ip address 192.168.0.1 255.255.255.0
ip verify unicast reverse-path
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
ip nat inside
ip virtual-reassembly
no ip mroute-cache
duplex auto
speed auto
snmp trap ip verify drop-rate
no mop enabled
interface GigabitEthernet0/1
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 2
interface ATM0/2/0
description ATM0_DSL
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
logging event atm pvc state
logging event subif-link-status
no atm ilmi-keepalive
dsl operating-mode auto
dsl enable-training-log
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface Dialer1
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
keepalive 1 3
no cdp enable
ppp lcp predictive
ppp authentication pap chap callin
ppp chap hostname ********@ccsleeds.net
ppp chap password 0 ********
ppp pap sent-username *******@ccsleeds.net password 0 ********
interface Dialer2
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
encapsulation ppp
dialer pool 2
keepalive 1 3
no cdp enable
ppp lcp predictive
ppp authentication pap chap callin
ppp chap hostname **********@adsllogin.co.uk
ppp chap password 0 *********
ppp pap sent-username *********@adsllogin.co.uk password 0 ***********
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
ip route 0.0.0.0 0.0.0.0 Dialer1
ip route 0.0.0.0 0.0.0.0 Dialer2 10
no ip http server
no ip http secure-server
ip nat inside source list 1 interface Dialer1 overload
ip sla 1
icmp-echo 8.8.8.8 source-interface di1
timeout 1000
threshold 100
frequency 3
ip sla schedule 1 life forever start-time now
access-list 1 permit 192.168.0.0 0.0.0.255
control-plane
gatekeeper
shutdown
line con 0
line aux 0
line vty 0 4
password test
login
scheduler allocate 20000 1000
end

Sure that EEM can shut/unshut interface...you have "event track" in EEM for monitoring track events...for example:
event manager applet test
event track 1 state down
action 1.0 command "enable"
action 1.1 command "conf t"
action 1.2 command "interfac dialer 1"
action 1.3 command "shut"
action 1.4 syslog "Dialer 1 down!!!"
action 1.5 end
This would be an example from head :)
You would need another EEM similar to this one for unshutting interface with "event track 1 state up" for bringing interface up again.
Again as I said you would need to test this before putting in production and you would maybe need to tweak this a little bit acording to your needs...
BR,
Dragan

BGP peering via default route

I read http://blog.ipexpert.com/2010/11/08/bgp-peering-and-default-routes/ and understood that BGP speaker will not initiate BGP connection with the other BGP router if it can reach it via default route only...And BGP peering will not come up at all if both the BGP speakers know each other via default routes only....I could not understand the reason behind this though...Could any expert help me in understanding the underlying reasoning?

I can't think of a reason why you would want to peer with a router you don't have a route for. If you're relying on a default route for a multi-hop bgp peer session, it could cause the session to be unreliable due to changes in the network down the line from you. An unreliable bgp session would be bad on the router's cpu/memory if the session were to flap.

Can the lifetime of default route (in RA) to the client be renewed?

The question is that why the "lifetime" for the "ipv6 nd ra" is set maximum 1800sec? It equals to just 30mins.
If this timer is expired, how to renew the RA to the client? If the renewal is not possible, the client will loss the default
route information forever. What is the solution for client not loss the default route (except the manual configuration)?
Thank you

Hi,
It's not really a lifetime at such. A non zero value means this router can be considered as a default-gateway.
From RFC 4861:
Router Lifetime
                     16-bit unsigned integer. The lifetime associated
                     with the default router in units of seconds. The
                     field can contain values up to 65535 and receivers
                     should handle any value, while the sending rules in
                     Section 6 limit the lifetime to 9000 seconds. A
                     Lifetime of 0 indicates that the router is not a
                     default router and SHOULD NOT appear on the default
                     router list. The Router Lifetime applies only to
                     the router's usefulness as a default router; it
                     does not apply to information contained in other
                     message fields or options. Options that need time
                     limits for their information include their own
                     lifetime fields.
Also please refer to http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_07.html#wp2360344
HTH
Laurent.

Default gateways and zones in a multihomed system

We do have some problems concerning default routes and zones in a multihomed system.
I found several posts in this forum, most of them referring to a domument of meljr, but my feeling ist that the paper is either not correct or not applicable to our situation?! Perhaps somebody can give me a hint.
Let me sketch our test environment. We have a multihomed Solaris 10 system attached to three different DMZ's using three different network adapters. We set up two local zones with IP's of the DMZ's of adapter 1 and 2, leaving adapter 0 for the IP of the global zone.
Now we set up default routes to ensure that network traffic from the local zones is routed in the corresponding DMZ's. That makes three different default routes on the global zone. On startup of the local zones, netstat reports the expected default routes to the correct DMZ gateways inside each zone.
Now what happens... My ssh to the global zone sometimes breaks. When this happens, no pings are possible to the IP of the global zone. Meanwhile, pings from other machines in our network (even from different subnets) might produce replies, some don't. By now, I can't tell you if there's is anything deterministic about it... More interesting: the local zone connections aren't affected at all!
So we did some more testing. Binding an IP address to the DMZ interfaces where the zones are tied to makes no difference (we tried both, with or without dedicated addresses for the adapter in the global zone). So the setup we're using right now is made of 5 IP addresses.
IP1, subnet 1: adapter 0, global zone
IP2, subnet 2: adapter 1, global zone
IP3, subnet 2; adapter 1. local zone 1
IP4, subnet 3; adapter 2, global zone
IP5, subnet 3; adapter 2, local zone 2
In the global zone there are three default gateways defined, one in each DMZ subnet. Inside the local zones, at startup you'll find the corresponding gateway into the DMZ. Everything looks fine...
I opened five ssh connections to the different IP's. Now what happened... After approx. half an hour, the connections to two IPs of the global zone (adapter 0 and adapter 1) broke down, while the connections to all other IP's were still open. This behaviour can be reconstructed!
So perhaps anybody has a explaination for this behaviour. Or perhaps anybody can answer me some qustions:
1. How are the three default gateways handled? Is there still some kind of "round robbin" implemenation? How can I guarantee that network traffic from outside isn't routed inside the DMZ's without preventing the local zones from talking to each other (actually we only need to communicate on some ports, but the single IP-stack concept only gives us all or nothing...).
2. If I do a ping from local zone 1 to the default gateway of local zone 2, this route is added as additional default gateway inside local zone 1! So does this mean, the routing decision is made only inside the global zone not taking into account where the packet is sent from?
3. After all, how are the IP packets routed from the different zone and the global zone, and how are they routed back to calling systems from the various DMS's and other networks, routed via these DMS's???
The scenario seems to be covered by http://meljr.com/~meljr/Solaris10LocalZoneDefaultRoute.html, but configuring the machine like stated in the paper leaves me with the problems described.
I'd be happy for any helpful comment!

you can have multiple gateway entries in deafultrouter file but the default gateway for global zone can be only one but you can specify different gateways for different zones..
using this default gateway, you should be able to connect via different network...!

A router should not see this default route concept ?

I have got Router3 connected between two different domains OSPF and EIGRB (Router3 is ASBR), if the requirement like this:
Configure your network so that Router3 advertises a default route to the rest of your OSPF enabled devices. However in order to help prevent traffic black holes, it has been suggested that Router3 should not see this default route. Instead Router3 must have a longer match for all destination.
What did he meant by : Router3 should not see this default route and Instead Router3 must have a longer match for all destination. ?

yes the default is 0.0.0.0/0
The router will issue a default into the ospf domain but when you check r3's routing table there will not be a default route...This instructs all other routers that have no specific route to a destination network, to send their traffic to r3.
When a router makes a routing decision it looks for the routing entry that best matches the destiantion. For example if it needs to route a packet to 10.1.2.0 and has the following entries in the routing table:
1. 10.0.0.0/16 next-hop A
2. 10.1.0.0/16 next-hop B
3. 0.0.0.0 next-hop C
It will chose B, because it is a longer match to the destination.
for a destination net 192.168.0.0 it would use the default

Stopping ISIS ipv6 (Multi Topology) Default Route

Dear Team
I am facing the following issue, not sure has it been worked out before.
We can stop Default Route on ISIS IPv6 Level-1 routers from nearest L1/L2 Routers, through set-attached-bit , when ISIS Ipv6 is deployed in Single Topology, with set attached bit default route is removed both ISIS Ipv4 & Ipv6 routing tables.
however
it does not work when ISIS IPv6 is deployed in Multi-Topology. I Applied to control it through Ipv6 prefix-list, but is not beneficial, as level-1 routers are still receiving the default route.
router isis
address-family ipv6
redistribute isis level-2 into level-1 distribute-list st
where distribute-list "st " specifically denies the default route and allow others.
ipv6 prefix-list st seq 1 deny ::/0 (Default Route)
ipv6 prefix-list st seq 2 permit 2002:19:19::1/128
ipv6 prefix-list st seq 3 permit 2002:19:19::2/128
How we can stop a default route on ISIS IPv6 Level-1 Routers injected from nearest L1/L2 Routers.
Any Help will be highly appreciated.
Thanks
Ahad

Hi ,
What I found is "
If there are parallel adjacencies to the same neighbor (on different interfaces) normal
IS-IS behavior is to suppress the advertisement of the additional adjacencies unless TE is
enabled. This redundant information is not needed in order to correctly run SPF.
Indication that the adjacency has been suppressed.
This should not be a cause of concern as it has no operational impact.
there is an Internal BUG for the same :
IS-IS Advertises Parallel Adjacencies when TE is NOT enabled
CSCum06418
Thanks-
Afroz
[Do rate the useful post]
***Ratings Encourages Contributors***

CSS advertise OSPF default route?

I have a CSS in one armed mode sitting between the Internet Edge router and PIX firewall.
The edge router is getting a default route from BGP and distributes that into the Firewall via OSPF.
The firewall sees the Edge router as the default gateway from the distributed route.
Would it be possible to have the CSS (through OSPF) get the default route from the Edge router and advertise it to the Firewall?
The goal is to have the Firewall use the CSS as it's default gateway, rather than the Edge router, but it needs to be a dynamic route.
In turn the edge router would pass traffic through the CSS to the firewall.
The CSS would be an intermidiate hop between the router and firewall.
Is this something that the CSS is capable of doing?
And from a design perspective, it is something that could be an issue?

Thanks,
I did see that document and played with it some last night.
I think it should work too, but was not sure if it was not reccomended by Cisco or not.
I have seen they they do not reccomend OSPF or RIP configurations, but I am only concerned with the default route and this would maybe solve the problem of any potential asymetric traffic flow.

Can anyone check this for me, nat overload, static and default routes, dhcp

VA has DHCP on fa0/0 and will have last good address for the gateway and will reserve 20 IP's for admin devices.
VA fa0/1 will be using static IP addressing and will be using the last good address as the default gateway address.
Serial links will use the 50.75.120.0/30 network on all serials.
Default route set to main via VAs next hop.
VA will be using NAT overload to Main via local interface.
VA
Fa0/0= 172.16.81.254
Fa0/1=172.16.82.126
S0/0/0=50.75.120.130
Main s0/0/1= 50.75.120.129 with a clock rate of 128kbps
Building configuration...
Current configuration : 1376 bytes
version 12.4
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
hostname VA
enable secret 5 $1$mERr$3nisV1NYMTmTN5PhTMBC2/
enable password insurance
ip dhcp excluded-address 172.16.81.235 172.16.81.254
ip dhcp pool VA-dhcp
network 172.16.80.0 255.255.254.0
default-router 172.16.81.254
spanning-tree mode pvst
interface FastEthernet0/0
ip address 172.16.81.254 255.255.254.0
ip nat inside
duplex auto
speed auto
interface FastEthernet0/1
ip address 172.16.82.126 255.255.255.128
ip nat inside
duplex auto
speed auto
interface Serial0/0/0
ip address 50.75.100.130 255.255.255.252
ip nat outside
interface Serial0/0/1
no ip address
shutdown
interface Vlan1
no ip address
shutdown
ip nat inside source list 1 interface Serial0/0/0 overload
ip nat inside source list 2 interface Serial0/0/0 overload
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/0/1
ip route 50.74.100.128 255.255.255.252 50.74.100.130
access-list 1 permit 172.16.0.0 0.0.255.255
access-list 2 permit 172.16.0.0 0.0.255.255
banner motd ^C
Restricted access to all unauthorized users, proceed at your will. Unauthorized users will be prosecuted to the extend of the law. ^C
line con 0
password shots
login
line aux 0
line vty 0 4
password xrays
login
end
VA(config)#
A network beginner, thank you in advance :))
Sent from Cisco Technical Support iPhone App

Reyna,
I can see a couple of issues
Your static routes:-
ip route 0.0.0.0 0.0.0.0 Serial0/0/1
ip route 50.74.100.128 255.255.255.252 50.74.100.130
Ser 0/0/1 is shut and has no ip addressing.
The route to 50.74.100.128 has no way to reach the next hop 50.74.100.130
Your NAT translations are both the same therfore only one is effective.
Just tidy up a little:-
The only static route you need is a default route:-
ip route 0.0.0.0 0.0.0.0 50.75.100.129
The NAT only requires one list and trans pointing out the outside interface
ip nat inside source list 1 interface Serial0/0/1 overload
access-list 1 permit 172.16.0.0 0.0.255.255
Regards,
Alex.
Please rate useful posts.

Default static route and Null 0

Hi Everyone,
Need to clear some doubts for below setup
Switch 3550A is connected to Internet Router and has OSPF nei relationship with it.
3550A#                      sh run int fa0/11
Building configuration...
Current configuration : 272 bytes
interface FastEthernet0/11
description OSPF LAN Connection to 2691 Router Interface Fas 0/1
no switchport
ip address 192.168.5.2 255.255.255.254
sh ip route shows
3550A#sh ip route
Gateway of last resort is 192.168.5.3 to network 0.0.0.0
O*E2 0.0.0.0/0 [110/1] via 192.168.5.3, 20:39:56, FastEthernet0/11
3550A#
All is working fine.
For testing purposes i config below static route on 3550A
ip default-network 192.168.1.0
ip route 192.168.1.0 255.255.255.0 Null0
After above change
3550A#           sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
S*   192.168.1.0/24 is directly connected, Null0
O*E2 0.0.0.0/0 [110/1] via 192.168.5.3, 20:38:38, FastEthernet0/11
Now i can not ping to internet as below
3550A#ping 4.2.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds:
Success rate is 0 percent (0/5)
When we ping from Switch then source IP is always the Outside interface IP right?
So in this case Switch is using which IP as source?
Ping to internet is not working as default network is set to 192.168.1.0 and all request goes to this IP and then it goes to
Null interface right?
Extended ping works fine as below
3550A#ping
Protocol [ip]:
Target IP address: 4.2.2.2
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.5.2
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds:
Packet sent with a source address of 192.168.5.2
Success rate is 100 percent (5/5), round-trip min/avg/max = 76/79/80 ms
Second thing to confirm is this ping works because 192.168.5.2 is directly connected to Internet Router interface?
Regards
MAhesh

Hi Mahesh,
When we ping from Switch then source IP is always the Outside interface IP right?
That is correct. By default it is always the outgoing interface on the device unless you specify it differently.
Ping to internet is not working as default network is set to 192.168.1.0 and all request goes to this IP and then it goes to
Null interface right?
That is correct. Null0 can't be used as next-hop.
Second thing to confirm is this ping works because 192.168.5.2 is directly connected to Internet Router interface?
No, that is because 192.168.5.0/30 is NATed. Remember 192.168.x.x address is a private segment and cannot access the Internet unless NAT is used.
HTH
Reza

Bought a new Ipod touch and the WiFi does not connect. Tried Reset and total Restore, does not connect to Router on DHCP, tried Static manually and still can not get it to connect even though it registers as connected.

Bought a new Ipod touch and the WiFi does not connect. Tried Reset and total Restore, does not connect to Router on DHCP, tried Static IP, Subnet, Router and DNS manually and still can not get it to connect even though it registers as connected. Using Airport for router, latest firmware, no problems with Iphone 4 or Macbook Pro or any other internet devices. After total Restore (factory settings) tried again, showed connected to router, but does not display "check" next to router but little rotating icon even though the wifi range signal shows connected at full strength and it says it is connected. Just can't seem to get it to generate an IP. Any solutions other than turning it on and off again? Not a Merry Christmas morning.

Ok, so, a couple of things: Denisefromwaleska and I have the exact same size/type/color iPod. Now wishing I'd bought the black one maybe...
Second, Airport is an Express and I have a second one that I carry with me when I travel. Tried to connect my Airport Express to the internet and could not although the iPod did recognize the router and tried to connect to the internet for some time, unlike my previous problem. Updated firmware on my travel router, still could not connect to the internet. Going to try to set up a manual Static IP on the travel router here in a few and conect through it although I predict the problem will persist. Back on the Christmas Present Airport Express router, it is back in play and working fine for all devices save the iPod.
Thanks again for all your help, hopefully I can get a solution in place soon,

Routing and Remote Access VPN DHCP error

I have a strange problem.
I have a client that is using Server 2012 Standard.
On this server they have Routing and Remote Access configured for VPN client access. Their users that are working outside the office connect to the VPN to access the internal network.
The VPN works fine for the most part. Recently however, it has started having issues.
Periodically (about once every 8 days) I will hear from them that they cannot connect and that they get error 720. I will check the server and the server will have the following errors in the event log:
Warning: No IP address is available to hand out to the dial-in client.
If you check DHCP the server is running fine and will hand out local addresses but it will not hand out addresses to VPN clients. Also the addresses that it HAS previously handed out to VPN clients will not show in the address leases.
The solution strangly enough is to disconnect and reconnect a the VPN client connection that the server has connecting it to a offsite server that it does a SQL sync with.
Any ideas as to what might be causing this? If need be I can post more detailed logs but I am not sure what logs even to post or what data to collect.
Any help is greatly appreciated.

I am experiencing the same issue on a Windows 2008R2 SP1 RAS server. The above statement About increasing the lease time on DHCP does not resolve the problem.
I am also Searching for a Solutions to this issue.
Up to now I have done the Following :
1. Increased the scope/ cleared IP's in DHCP.
2. Ensure that the DHCP server is accessable.
3. Created a Manual Scope on RRAS configurations settings (then clients can connect but cannot access resources on the network). Changing Back to DHCP, you recieve the same 720 Error.
4. Stop and started the DHCP services on the DHCP Server.
5. Stop and Started RRAS Services on RRAS server.
The Only Indication is, that DHCP for some reason does not lease out Addresses to the RRAS server..

I've just changed my router and whilst my laptops sync ok, my G4 tower which connects via an airport express doesn't connect to the internet. I think it's something to do with the IP or DHCP settings but have had no success, any help much appreciated.

I've just changed my router and whilst my laptops sync ok, my G4 tower which connects via an airport express doesn't connect to the internet. I think it's something to do with the IP or DHCP settings but have had no success, any help much appreciated.

Hi Jake,
Is it connecting to the Router or Modem?
Is the new Router using maybe WPA2 encryption? If so, G4s can only do WPA or less.
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
old... http://docs.info.apple.com/article.html?artnum=106653
Hi, this has worked for a few...
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
The Interface that connects to the Internet, needs to be drug to the top of System Preferences>Network>Show:>Network Port Configurations and checked ON.
Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
Then... Try putting these numbers in Network>Airport>TCP/IP>DNS Servers, for the Interface you connect with...
208.67.222.222
208.67.220.220
Then Apply.
Also, turn off IPv6:
System Preferences » Network » AirPort » TCP/IP tab » Configure IPv6

Default router and DHCP

Similar Messages

Maybe you are looking for