<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 12-Nov-08, at 4:35 PM, Matthew Simmons wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">Another question, are you using a router or firewall on the server. If so, ports will need to be open to allow full connectivity to the server. The ports that need opened are listed below:<br><br>28960 - UDP and TCP<br>20500, 20510, 20600, 20610 - UDP<br><br>For information on how to do this, visit:<br><br><a href="http://portforward.com/default.htm">http://portforward.com/default.htm</a><br></span></blockquote></div><br><div><br></div><div>As mentioned in a few of the other emails, I have disabled the firewall to take it right out of the equation.</div><div><br></div><div>But the one good bit of info from this email is that I had never seen reference to the 20600, 20610 ports. So I will add that to my list for when i do add the firewall back into play.</div><div><br></div><div>d</div><div><br></div><div><br></div></body></html>