We have an ADSL connection hooked up to a router. The router is networked via a hub with 2 other computers. We have had an account with Pipex for the last year and everything has been ok, but unfortunately it was mistakenly cancelled a few weeks ago. We have signed up with Virgin broadband, but now the router crashes every time it logs on.
The router is a Conexant CA61E Ethernet Router. When it is switched on, it goes through the logging on process, connects and everything appears to be fine. Then after a (varying) period of time it simply crashes - the only solution is to reset it. The log looks like this before it crashes:
1/1/1970 0:0:0> Ethernet Device 0 Detected
1/1/1970 0:0:0> ATM: Detected
1/1/1970 0:0:0> ATM: Setting up vcc0, VPI=0, VCI=38
1/1/1970 0:0:0> NAPT is enabled
1/1/1970 0:0:0> Initialized NAPT.
1/1/1970 0:0:41> ATM Connected
1/1/1970 0:0:41> ATM layer is up, cell delineation achieved
1/1/1970 0:0:41> ADSL connected
1/1/1970 0:0:41> PPP1 PPPoA Connected
1/1/1970 0:0:48> PPP CHAP Authentication success
1/1/1970 0:0:48> PPP1: PPP IP address is 81.107.202.104
1/1/1970 0:0:48> PPP1: PPP Gateway IP address is 81.107.223.254
1/1/1970 0:0:48> PPP1: DNS Primary IP address is 194.168.4.100
1/1/1970 0:0:48> PPP1: DNS Secondary IP address is 194.168.8.100
1/1/1970 0:0:48> NAT/NAPT Session Start: VC# 0, WAN IP is 81.107.202.104
1/1/1970 0:0:48> Initialized NAT Virtual Servers.
1/1/1970 0:0:48> NAPT: Pipex session is up.
1/1/1970 0:0:49> PPP1 Session is up.
8/23/2003 11:58:12> Received time from Time Server 129.6.15.29
I don't think it's connecting to the time server that causes the crash because it doesn't happen immediately afterwards. There doesn't seem to be any way of finding out what causes the problem...
We have tried using the BT test account (username: bt_test@startup_domain, etc) and it has no problems. So there must be something wrong with the setup rather than the hardware, right??
Please help - we are extremely confused and frustrated!
Mark
The router is a Conexant CA61E Ethernet Router. When it is switched on, it goes through the logging on process, connects and everything appears to be fine. Then after a (varying) period of time it simply crashes - the only solution is to reset it. The log looks like this before it crashes:
1/1/1970 0:0:0> Ethernet Device 0 Detected
1/1/1970 0:0:0> ATM: Detected
1/1/1970 0:0:0> ATM: Setting up vcc0, VPI=0, VCI=38
1/1/1970 0:0:0> NAPT is enabled
1/1/1970 0:0:0> Initialized NAPT.
1/1/1970 0:0:41> ATM Connected
1/1/1970 0:0:41> ATM layer is up, cell delineation achieved
1/1/1970 0:0:41> ADSL connected
1/1/1970 0:0:41> PPP1 PPPoA Connected
1/1/1970 0:0:48> PPP CHAP Authentication success
1/1/1970 0:0:48> PPP1: PPP IP address is 81.107.202.104
1/1/1970 0:0:48> PPP1: PPP Gateway IP address is 81.107.223.254
1/1/1970 0:0:48> PPP1: DNS Primary IP address is 194.168.4.100
1/1/1970 0:0:48> PPP1: DNS Secondary IP address is 194.168.8.100
1/1/1970 0:0:48> NAT/NAPT Session Start: VC# 0, WAN IP is 81.107.202.104
1/1/1970 0:0:48> Initialized NAT Virtual Servers.
1/1/1970 0:0:48> NAPT: Pipex session is up.
1/1/1970 0:0:49> PPP1 Session is up.
8/23/2003 11:58:12> Received time from Time Server 129.6.15.29
I don't think it's connecting to the time server that causes the crash because it doesn't happen immediately afterwards. There doesn't seem to be any way of finding out what causes the problem...
We have tried using the BT test account (username: bt_test@startup_domain, etc) and it has no problems. So there must be something wrong with the setup rather than the hardware, right??
Please help - we are extremely confused and frustrated!
Mark