I have problem running my IRCd for Windows, when I try to connect to 127.0.0.1 on port 7000 (/server 127.0.0.1:7000), the daemon says
** Connecting to 127.0.0.1 (7000) - * Identd request from 127.0.0.1 * Identd replied: 1438, 7000 : USERID : UNIX : ScAR - [Server Notice] *** If you are having problems connecting due to ping timeouts, please type /notice FC5446F6 nospoof now. - Password Incorrect - Closing Link: Abcent[localhost] (Bad Password) - * Disconnected*
**
*What is wrong? I am sending you ircd.conf, please help as I am much interested in running my LAN server :)
*-- Anticipating your reply, S.A.Rahman Bukhari MSN: abcent@gmail.com Gmail: s.a.rahman@gmail.com Blog: http://abcent.iblog.com/ Album: http://www.flickr.com/photos/abcent/ Cell: 00923212850223 MySpace: http://www.myspace.com/a2850223 Confidentiality Notice:- This e-mail and any attachments may contain confidential, privileged or proprietary information.If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail (with any attachments) and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal.
might want to check your config file and make sure your i-lines are properly configured?
On Jan 29, 2008, at 9:10 AM, Syed Abdur Rahman Bukhari wrote:
I have problem running my IRCd for Windows, when I try to connect to 127.0.0.1 on port 7000 (/server 127.0.0.1:7000), the daemon says * Connecting to 127.0.0.1 (7000)
- Identd request from 127.0.0.1
- Identd replied: 1438, 7000 : USERID : UNIX : ScAR
[Server Notice] *** If you are having problems connecting due to ping timeouts, please type /notice FC5446F6 nospoof now.
Password Incorrect
Closing Link: Abcent[localhost] (Bad Password)
- Disconnected
What is wrong? I am sending you ircd.conf, please help as I am much interested in running my LAN server :)
-- Anticipating your reply, S.A.Rahman Bukhari MSN: abcent@gmail.com Gmail: s.a.rahman@gmail.com Blog: http://abcent.iblog.com/ Album: http://www.flickr.com/photos/abcent/ Cell: 00923212850223 MySpace: http://www.myspace.com/a2850223 Confidentiality Notice:- This e-mail and any attachments may contain confidential, privileged or proprietary information.If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail (with any attachments) and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. <ircd.conf>_______________________________________________ DALnet-src mailing list DALnet-src@lists.dal.net https://lists.dal.net/mailman/listinfo/dalnet-src
Seriously... shouldn't dal4.4.13 for Windows be pulled at this point, or placed into an archival location clearly indicating it is old and unsupported? The version is buggy, the build is old and (IMO) antiquated. One can barely remember dal 4.4's idiosyncracies.
My suggestion is that: if there is a windows version available at all outside of clearly marked 'archives': it should be the same as the current version for all OSes and not have a different codebase or contain special code like '#ifdefs' to specifically cater to Windows.
I would see the optimal target as Windows Advanced server 2003 with the POSIX extensions, and possibly 2008 as a marginal (bleeding edge) target.
As the Windows desktop OSes have crippled TCP/IP capabilities, sometimes crash or frequently experience instability, and are not at all suitable for running a sizable IRC server.
In contract, Server 2003 properly configured and with the right hardware certainly is very stable and suitable for running large servers. It is routinely used by enterprises to run other types of servers with much higher I/O and traffic loads than IRC.
The IRCD software just doesn't run on that platform, because IRC started as a UNIX application, and it is more convenient to just run UNIX servers than port. Porting requires time and energy resources that are difficult to justify, given the specialized nature of the application.
There mere cost of the Windows server OS can buy some significant hardware to run a free UNIX clone on, for a large IRC network, multiply the cost by the number of servers, and see....
With the additional benefit that UNIX servers extract additional performance out of hardware; less GUI/API overhead, and on equivalent hardware, UNIX has better performance.
Still, a proper Windows port might make more good servers available than would be available otherwise (very small possibility).
-- -J
On Tue, Jan 29, 2008 at 9:10 AM, Syed Abdur Rahman Bukhari abcent@gmail.com wrote:
I have problem running my IRCd for Windows, when I try to connect to 127.0.0.1 on port 7000 (/server 127.0.0.1:7000), the daemon says * Connecting to 127.0.0.1 (7000)
-
Gabriel Baez -
James Hess -
Syed Abdur Rahman Bukhari