Subj : Re: Barren Realms Elite To : Frank From : Sniper Date : Tue Sep 20 2005 07:05 pm -=> Frank wrote to Sniper <=- Fr> Re: Re: Barren Realms Elite Fr> By: Sniper to Frank on Mon Sep 19 2005 10:31 pm > Think of it this way... if someone can do an http://thedarkcastle.net or > ftp://thedarkcastle.net, then the domain is working. All the domain does > is point the name "thedarkcastle.net" to your "IP" which happens to be > 64.202.167.129. That is the end of what godaddy does. Any traffic for > thedarkcastle.net is directed to the IP, end of story. Its your ISP that > blocks inbound/outbound ports... Fr> It's a Windows XP system w/SP2. Actually I was disapointed that it Fr> wouldn't work with the telnet prefix. At the GoDaddy site when I Fr> enter Fr> the IP address with the telnet the site returns that a telnet is Fr> invalid. Fr> That's not a verbatum quote but pretty much the jist of it. But when Fr> you Fr> put an HTTP prefix on the IP address it works. I won't rule out Fr> operator Fr> error on my part but as it was I did what I had to do to get it to Fr> work. The possibilities are many... since your running XP with Service Pack 2, that means you have a firewall involved... not to mention that you may have another one... ZoneAlarm, etc... already involved. Toss in the configuration of the DSL Modem/Router for the Network Address Translation (NAT), and you've got a headache... :) Fr> I run simple server on one machine and run my HTML script on it and Fr> direct Fr> incomming HTML calls to that computer with the router firewall. In Fr> the Fr> script is an href command that when clicked on calls the telnet Fr> address to Fr> the computer the BBS is running on. It may be the long way around the Fr> barn Fr> but it's all I knew to do. I am in now way ready to take on the 32 Fr> bit side Fr> of Synchronet. First, from the BBS computer itself, open a DOS window and type "telnet localhost" (Without the quotes). Do you get a connection? Next, from that same DOS window, type ipconfig. Look for the "IP Address" line, and then from a different computer, open a DOS window and type in telnet and the IP you got from the ipconfig. Can you connect? What this tells us. If you can telnet localhost from the BBS computer and it answers, then all is well there. If you can telnet from a second computer to the IP address of the BBS computer, then there's nothing blocking the port and all is well on the external side of the BBS computer. If you can't, then either a firewall is in the way, or there's something else blocking the external side of that machine. Read on for the next step talking about firewalls. If you can telnet from another "Internal" computer to the BBS, then the problem is in the router. Probably the NAT table. One thing to make sure of is that you have assigned a static internal IP address to your BBS machine. In my case, my network is on the 192.168.1.xx range. My BBS computer is 192.168.1.25, so from any of my other computers, I can telnet to 192.168.1.25 and my BBS answers and I can telnet in. So in my westell router, I went into the expert section, under configuration, and opened the section called NAT. I scrolled through the list of preconfigured NAT's and found the telnet one, clicked on it. It then pops up a window asking where I wanted to point that port... "Host Device". Now, in my sitation, the first time, it listed in the drop down box, by IP addresses... I found the 192.168.1.25 listed and selected it. But now, I've updated the firmware and it now shows it by the UNC name... My BBS computer is called "BBS". :) So, I pick that. So now, Telnet is directed to the BBS computer. Now you have to save that configuration, and I like to restart the device to make sure it keeps the settings... but it should start forwarding in that port as soon as you create it. From here, you just create each port you want to use for your BBS systems. At http://www.synchro.net/docs/tcpip_faq.html will tell you what all ports are used for your BBS. Another way to do this, which I think I spoke about already is again, under the expert section, configuration, click on the IP Passthrough, and again, pick your BBS computer's name or IP address... I'm going to say this again, this is dangerous, because it points anything inbound to your BBS computer. I mean, all ports are now forwarded in. Using this, a firewall on the BBS computer is a must have!!! Danger Danger! But that leads us to the next part... Firewalls. If you have a firewall running on your BBS PC, you have to enable "Exceptions". Again, the above listed website gives you a list of ports, but you have to create each port, UDP or TCP and enable it. To get to the Windows XP SP2 Firewall, Right click on the My Network Places, properties, find your local area connection, and right click on it, select properties, then click on the tab Advanced. Click the Settings button under the Windows Firewall. Click on the tab Exceptions. Now in here, this is where you create each of the exceptions needed for your BBS... Telnet, FTP, SMTP, POP3, NNTP, IRCD, Finger, Gopher, etc... Fr> Anyhow thats what I'm doing and why. There's my lesson on setting up a computer to run SynchroNet. :) I was hoping you'd give me a call cause I knew this would be a "Long" post. But, maybe someone will capture it and post it in the DOC section for setting up a Westell DSL router. Sniper Killed In Action BBS, telnet://kiabbs.org Home of the Unofficial SynchroNet Support Network. download the info pack at any of the below sites: http://www.chcomputer.net/USSNET.ZIP or http://www.ussnet.org .... Small changes pick up the reins from nowhere --- MultiMail/Linux v0.46 þ Synchronet þ Killed In Action - telnet://kiabbs.org .