1  |   Order by index

Apr 17, 2001, 9:26am

Hi,

I started to make a webpage describing how to run AW and/or the world server behind routers or firewall. Experiences, descriptions, comments are welcome - criticism will go to the bitbucket. I would be pleased if some more experienced HTML guru would revise/rewrite the page <hint hint>

Andras

http://andras.net/router_aw/router_aw.html

Apr 17, 2001, 12:10pm

[View Quote] Yay Andras - the BANE of my existance

*spits in the general direction of NAT routers*

hahaha

Facter
AW Support

Apr 17, 2001, 12:36pm

[View Quote] I don't think I can incorporate "spit" on a webpage :)
Andras

Apr 18, 2001, 7:17pm

[View Quote] Added detailed instruction for ZoneAlarm Pro.

Andras

Apr 18, 2001, 8:55pm

Everything looks good, Andras, except for a few things. You say that you
should open UDP port 53 (DNS) if hosting a server, yet you may also need
to add it to the Active Worlds Browser to determine the auth server's IP
address as well as world object path IP addresses. Also, I have been
hosting several worlds for months now without ever needing to open any
UDP ports on admin.exe or winworld.exe (not even UDP port 53) and have
not encountered any problems.

There is one thing to note however about restricting port access in
ZoneAlarm Pro. Not all hosters use the 7000 - 7999 port range to host
their world servers on. If you cannot access a certain world, look in
the "Alerts" tab of ZoneAlarm Pro to see if a port was trying to
communicate with the Active Worlds Browser. You will see a message like:
"Active Worlds Browser was not allowed to connect to XXX." Add that port
in your Active Worlds Browser rule in ZoneAlarm Pro and you should then
be able to enter.

Finally, the settings on your page do not account for the use of the
built-in browser (Internet Explorer). You will probably need to add TCP
ports 1024 and up to be able to use the built-in web browser. Besides
these small flaws, I appreciate you creating that page to help fellow
firewall users of Active Worlds technology. If a newbie ever asks "How
do I configure AW to work with ZAP?", I can safely refer them to your
page and use my time saved trying to help them configure ZAP for better
things. :)

Builderz
Stuff-X - Bot & World Hosting Services
http://www.stuffx.com/aw/

[View Quote]

Apr 18, 2001, 9:49pm

inline....
[View Quote] To be honest I did not have the DNS prot open but I mentioned it just in case someone runs into it as a problem. (My DNS server is actually on the local zone - I have my own DNS server)

>
> There is one thing to note however about restricting port access in
> ZoneAlarm Pro. Not all hosters use the 7000 - 7999 port range to host
> their world servers on. If you cannot access a certain world, look in
> the "Alerts" tab of ZoneAlarm Pro to see if a port was trying to
> communicate with the Active Worlds Browser. You will see a message like:
> "Active Worlds Browser was not allowed to connect to XXX." Add that port
> in your Active Worlds Browser rule in ZoneAlarm Pro and you should then
> be able to enter.

Added to the webpage.

>
> Finally, the settings on your page do not account for the use of the
> built-in browser (Internet Explorer). You will probably need to add TCP
> ports 1024 and up to be able to use the built-in web browser.

Strangely enough the built in browser connects through UDP port in the range of 2900-2999 (at least those tests I made all fell within this range)

> Besides
> these small flaws, I appreciate you creating that page to help fellow
> firewall users of Active Worlds technology. If a newbie ever asks "How
> do I configure AW to work with ZAP?", I can safely refer them to your
> page and use my time saved trying to help them configure ZAP for better
> things. :)
>
> Builderz
> Stuff-X - Bot & World Hosting Services
> http://www.stuffx.com/aw/
>

Thanks for the comments. With your "implicit" permission I used your correction's phrasing on the webpage :)

Andras

Apr 18, 2001, 10:36pm

Please see my comments below:

[View Quote] > To be honest I did not have the DNS prot open but I mentioned it just in case someone runs into it as a > problem. (My DNS server is actually on the local zone - I have my own DNS server)

You are correct. I forgot about users that have/run a local DNS server
such as yourself. *smacks himself* =)

> Strangely enough the built in browser connects through UDP port in the range of 2900-2999 (at least those > tests I made all fell within this range)

Hmm...I tested it and it started at around UDP port 2001. I think it
tries to use the first port not already in use to connect to a website,
which can vary on system to system. For example, if I just freshly
rebooted my system, it may try to connect on UDP port 1037 while someone
who has been doing heavy web surfing, downloading, etc. prior to using
the browser may connect at UDP port 3011.

> Thanks for the comments. With your "implicit" permission I used your correction's phrasing on the webpage :)

Although it'd be nice to have a link back to Stuff-X... (just kidding)
that is fine by me. =) Again, great work on the page and I hope it will
benefit many people.

Builderz
Stuff-X - Bot & World Hosting Services
http://www.stuffx.com/aw/

1  |   Order by index