Table of Contents
Advertisement
If the IPCP state is 'Starting' and the various IPCP IP values are 0.0.0.0 then you AREN'T logged into the ISP. You
should have 'sensible' IP values here for 'local options IP address' and also 'remote options IP address'. If DNS relay
(with autodiscover) is on then you should also have sensible values for the DNS IP.
If no connection then things to check:
I. Obviously look at the user name and password. Are these correct. e.g. for Pipex the correct format of the user name is
'userID@dsl.pipex.net'.
II. For the Asus make sure that the 'PPP Starting Status' (on the second screen of the Channel set-up) is set to UP. If not
then the router won't auto login.
III. Also for the Asus check that DOD (Dial On Demand – on the second screen of the Channel set-up) is not enabled. If it
is then the router will need to detect some local traffic before it will login.
IV. Check the VCI/VPI/Encapsulation. Get it wrong and it won't login (not settings for KC are different than for BT).
V. Try the BT test account:
Enter the user name of bt_test@startup_domain
The password doesn't matter.
NAT on.
Save settings and reset.
After Synch then check the PPP status again.
If now connected then the problem is with the ISP not letting you login with them.
(please note that using the bt test account the only web site that will work is www.bt.net/digitaldemo and you must be
using the bt_test DNS – see DNS list below)
VI. Lastly faulty router (but very unlikely – more likely line not set-up right by ISP/BT).
3. IP settings on Computer(s)?
Things to check:
I. Can you ping the router from the computer?
No?
Check IP address of computer is suitable (same subnet).
Can you ping yourself? e.g. if computer is 192.168.0.2 then can you ping 192.168.0.2? If not the IP set-up on
computer is really knackered. Removes ALL LAN settings on the computer and reinstall.
Check no clashes with any other computers (or net printers) on the LAN. Best to try normal LAN cable direct from
router to computer LAN card/port. If okay then check other computers/hubs/wiring.
Check LAN cable: You should have a 'PC' light on on the router (or for BI/VI the LAN light on the port should be
on) and also the 'link' light on the hub/PC LAN card should also be on.
Check LAN card.
Try removing ALL LAN set-up on computer and also LAN card installation. Reinstall and try again.
II. So you can ping router. Can you ping the DNS?
If you don't know this and using DNS relay (with auto-discover) then check the 'IPCP primary DNS server' setting
for the DNS address.
No joy?
Check 'default gateway' on computer.
For Win 95/98/ME run 'winipcfg' to check this.
For NT4/2K/XP run 'ipconfig \all' in a DOS box.
Possibly might have some 'wrong' routes set-up on computer. Remove ALL LAN settings and
reinstall.
III. So you can ping the DNS (or outside address).
Does the computer have DNS enabled?
Check the DNS settings in TCP/IP set-up. DNS is enabled yes?
Does the computer have a valid DNS entry. Check winipcfg or ipconfig (see above). Note if using DNS relay
then DNS address on computer should be the same as the gateway. Also, if using DNS relay ensure that
'IPCP primary DSN server' has a sensible IP address (0.0.0.0 is not sensible!).
4. Browser set-up.
So the router's working and the basic IP settings on the PC are correct (e.g. you can correctly ping the external DNS).
Common browser problems:
I. IE set to dial up when it should be using LAN – set connections to 'Never Dial a Connection'.
II. Browser set to 'work offline'
- 17 -
Advertisement
Table of Contents
