More than
likely the client is trying to connect when not disconnected correctly provide
a detail of the pppoe server log for the connection and we can see where it is
failing
619
There are
several possible reasons why a connection to the remote computer could not be
established:
|
•
|
The
remote computer might have been too busy. Wait a few minutes and try the
connection again.
|
|
•
|
If you
are trying to establish a dial-up connection, you might have tried to redial
before the modem fully disconnected. Wait a short time and try your call
again.
|
|
•
|
If you
are trying to establish a connection by using a modem, the modem might not be
functioning properly. For more information, see Troubleshooting modems.
|
|
•
|
If you
are using a device such as a router, a hub, or a network adapter for network
address translation (NAT), the device might not be functioning properly. If
the device provides firewall capabilities, the device might be blocking the
connection. Consult the documentation for the device.
|
From: alan walters
Sent: 11 July 2006 17:40
To: support@pfsense.com
Subject: RE: [pfSense Support]
PPPOE Server
It failes after saying registering on
network???
Or what sequence does it go through before
it failes
From: juan pablo burd
[mailto:[EMAIL PROTECTED]
Sent: 11 July 2006 17:27
To: support@pfsense.com
Subject: RE: [pfSense Support] PPPOE
Server
Via
ethernet, connected with winpoet
De: alan walters [mailto:[EMAIL PROTECTED]
Enviado el: Martes, 11 de Julio de
2006 01:12 p.m.
Para: support@pfsense.com
Asunto: RE: [pfSense Support]
PPPOE Server
Mtu issue most likely, we see this problem
also if the client continues to authenticate
Without waiting.
Is this on a wired port???/
From: juan pablo burd
[mailto:[EMAIL PROTECTED]]
Sent: 11 July 2006 14:17
To: support@pfsense.com
Subject: [pfSense Support] PPPOE
Server
I have the problem
Clients Windows 2000 profesional no
connect with pfsense pppoe Server (error 619), other (XP,98,95 2003)
yes…. why
__________ Informacisn de NOD32, revisisn 1.1653 (20060711) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
