Unreal Tourny Server PROBLEM!!

[meaty]

OK here's the situation:

I have two computer's & @ home cable with two different IP addresses.

I can set up the server to where everyone can play on it , but I cannot get in myself? I have tried connecting several different ways(eg. IP, unreal IP, IP port # etc..).
I have tried changing the port #'s on both machines to several different one's but still same thing it hangs @ connecting?
Another people have went in there & played on it. I dont have a firewall that I am aware of ( i did not install anything). I tried all the diff versons of UT on both systems. I have used the same cd for both (with nocd patch) & have used 2 different cd's. I have tried renaming the server computer.
Here is what the cable line is runnin through:
Motorola cyber surfer modem
SMC ether EZ hub (model 3605t)

I have tried putting them into different ports on the hub.
This is the thing that gets me, I can surf the net on both computer @ the same time? In totally different web sites( 2 IP addresses). Wouldnt that mean it should just be working?
I know its possable becuase people have done what i'm doing.

Please help

I am a newbie to serving so if you have any questions LMK, thanks meatNbonz

 

[Poof]

Meaty - I have @home too and at least you can get both your IPs going out at the same time! With me, it's one at a time (grrrrrr.....:|), even though the model modem is supposed to support multiple IPs. I've gotten around it with NAT for the time being... There's something with those damn CyberSurfers that's wierd as sh1t! It's been driving me crazy for over a year...

Try this - from the machine that you play on, open up a DOS prompt (I'm assuming you running Windows) and at the prompt type:

ping www.xxx.yyy.zzz

where "www.xxx.yyy.zzz" is your server's address.

If the response is something like:

Reply from www.xxx.yyy.zzz: bytes=32 time<10ms TTL=225
Reply from www.xxx.yyy.zzz: bytes=32 time<10ms TTL=225
Reply from www.xxx.yyy.zzz: bytes=32 time<10ms TTL=225

Ping statistics for www.xxx.yyy.zzzz:
blah blah...

then at least your gaming machine knows your server exists. If you don't get the above or equivalent, ie., you get:

Request timed out.
Request timed out.
Request timed out.

then your gaming machine doesn't see your server and you may want to modify your gaming machine's c:\windows\hosts file to make sure that the servername and numerical IP are entered in there. Also make sure that your gaming machine has the DNS info filled out in the Network properties (from your @home service - normally it's blank because most of the @home's use DHCP to give you your address, even when it's &quot;static&quot;, and that process also gives your machine the DNS info, but perhaps in your case, it didn't work as advertised...).

As a possible work around for gaming - just to be able play until another solution presents itself (and to test something that I'd like to know the answer to), try redoing the IP address on your gaming machine, changing it to one of the restricted IPs, eg., 192.168.0.1. Give the machine whatever hostname you want. Set the gateway in your Network properties in your gaming machine to your server's IP. Then try connecting to your server again...

It may not be you but that damn cable modem.... And no, those Cybersurfers don't have any built-in firewalls...

 

[meaty]

How do I modify the host file? What sould I enter in the DNS area?
thnx for all the help

 

[Poof]

You can edit the hosts file using Notepad. I think there's a &quot;hosts.sam&quot; file in c:\windows that has examples of how the format should be. You can use that file to add your server IP, then do a &quot;save as&quot; and save it as plain old &quot;hosts&quot; (with no extension).

With respect to a DNS, you need to find out what your local one is. I think with @home, they point everyone to their own default excite@home start page. On there somewhere (probably at the top), there should be a link that says &quot;Member Services&quot;. If you click that, you should hopefully get to someplace where they have a link for how to do &quot;Networking&quot;. On my @home, at that point, there's an option for me to login to @home (account management) and then I can select a link that will tell me my assigned IPs. From that page, they had links for those who wanted to install @home on 95/98, Mac, and NT - and if you select the NT page, it showed me how to manually set the Network Properties, including giving me the IPs for the local DNS servers. It'll probably be the same IP as your @home gateway (at least mine is) and there's usually 2 of them you can enter (so there's a backup DNS).

I know this sounds kinda convoluted but hope this helps some!!!