|
||
|
|||||||
| General Discussion General discussion for the RunUO community, all off-topic posts will be deleted. This forum is NOT FOR SUPPORT! |
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Forum Expert
|
I am currently having a problem with people connecting to my shard. It won't seem to forward people with the no-ip bit.
According to them, my IP is correct....i have my router and what not set up properly....so i dunno what the problem is. ![]() |
|
|
|
|
|
#2 (permalink) |
|
Forum Expert
Join Date: Apr 2006
Location: The Great White North!
Age: 33
Posts: 887
|
If you could provide a bit more information, that would certainly help figure out the source of the problem.
Have you properly edited your ServerList.cs? What does the RunUO Server Console window say when someone tries to connect? Does it say anything? Have you tried something like canyouseeme.org to determine if your port is correctly opened? Have you verified your IP is still the same by using something like whatismyip.com? IIRC, dynamic DNS services like no-ip.com require you to run a small client on your system to automatically update your IP... is that client running and performing its task? So, the more information you can provide, the better.
__________________
I R GEEK! |
|
|
|
|
|
#4 (permalink) |
|
Forum Expert
Join Date: Apr 2006
Location: The Great White North!
Age: 33
Posts: 887
|
If nothing makes it to the console, then you may want to try a few things to make sure it's not your router that's causing the problem or it's not no-ip.com.
Go to canyouseeme.org and see if it still says your port is opened. It will also tell you if the port is being blocked along the route to your server (ie. by your ISP for instance). Try to ping to a destination beyond your router... by name and by IP. For instance ping Microsoft's site or something, then ping something like 4.2.2.4 (which is the IP address of a public DNS server). Failure to get a response by name means there is a DNS problem (which may also affect your DDNS name resolution)... failure by IP means there's a routing problem. Go to whatismyip.com and see what your public IP is. Ping your DDNS name to make sure that the IP address that it returns is the same as the one that whatismyip.com reported (if it's different, there's may have been a problem updating your DDNS entry). At the same time, make sure your no-ip.com client is still running and updating your DDNS record. Those are just a couple things off the top of my head you can try. No guarantees these will point out any problems.
__________________
I R GEEK! |
|
|
|
|
|
#6 (permalink) |
|
Forum Expert
|
It seemed to have resolved itself. But it worked with just the IP addy of mine. the reason it was a problem was due to the fact that i couldn't get logged into gateway to change anything either so...it was a pain lol
thanks for the suggestions...thing that sucks is that i didn't get to really figure out what had caused it. ![]() *shrug* oh well |
|
|
|
|
|
#7 (permalink) |
|
Forum Expert
Join Date: Apr 2006
Location: The Great White North!
Age: 33
Posts: 887
|
It's just a guess but it almost sounds like your DDNS name wasn't resolving or even resolving to the wrong IP. There's quite a few reasons I can think of that might have caused that. But hey, glad to hear it's working now!
![]()
__________________
I R GEEK! |
|
|
|
|
|
#8 (permalink) |
|
Forum Novice
|
I use no-ip... and it seems like right after my WAN IP changes people can't connect. But that is only for about 5 min. or less so I doubt that was your issue. You are running it in the background right? That way it checks your IP often in case it magically switches on you.
__________________
Meh. |
|
|
|
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|