Dedi-box connection problem

Started by Supanova, Sep 14, 2009, 19:56:59

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Supanova

Hello to everyone. I realise this is not technically an IDnet problem, but I was unsure where to write the thread so please do move it if it's in the wrong place.

I'm usually pretty good with computers however I'm totally stumped on this one so here I am begging for help from the wiser.

I play CoD4 with my clan on their 3 CoD4 servers and Teamspeak Server. We recently had to change to a different dedi-box to the one we have been using to host all our servers and since then I have no been able to connect to, ping or see any of the servers on the new box.

The rest of the clan appear to be having no problems, and I am absolutely sure I am using the same IP addresses and ports to connect as they are. In CoD4 even if I follow a clanmate into on of our servers using x-fire the connection will still timeout. Teamspeak tells me the server is not running (meaning It can't communicate with it to authenticate me).

I can connect to the other 16,000 servers on CoD4 and I can connect to other TS servers. The question really is, is it my fault or is it the dedi-box?

The fact that all my clanmates are having no problem indicates it is my fault, but the fact that I can use the 16,000 other servers without a problem indicates it is the dedi-box.

Has anyone seen a problem like this before.

I'm running windows7 professional (obtained through university) on an almost fresh install. Thanks to any posters.
"Privacy is dead, deal with it" - CEO Sun MicroSystems

Simon

I'll move this to the Gamers' board, if that's OK, but if you don't get any luck here, my suggestion would be to talk to IDNet.  :)
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Could it be the ports for your new box are being blocked by your firewall?
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Supanova

Quote from: Lance on Sep 14, 2009, 22:45:10
Could it be the ports for your new box are being blocked by your firewall?

I can't imagine how. The dedi-box has its own IP obviously, and then the virtual servers hosted by the box are accessed via the different ports. The thing is the entire box ip is just not responding to me.

Here's a screenshot I used while talking to the wall that is our server host. Ping Tests. It's really really odd. The successful pings were to an almost identical server hosted by a different clan. It's just my clans dedibox that's the problem.

I might ring IDnet tomorrow and see if they can help if nothing else comes up. If they can't I'll get them to give me a new IP address incase I'm being IP blocked or something - doubt it will help though.

  :-\
"Privacy is dead, deal with it" - CEO Sun MicroSystems

somanyholes

can you post your tracert output.

Supanova

#5
Sure.

http://img171.imageshack.us/img171/3284/tracertx.jpg

goscomb.net is an internet hosting service which I assume has gamingdelux (the dedibox server host) as one of their projects.

Looking at a tracert to a gamingdelux server someone else on the web did the next (and last) step in the tracert should be:

78.gamingdeluxe.co.uk [91.192.210.92]
"Privacy is dead, deal with it" - CEO Sun MicroSystems

Supanova

gamingdelux tell me the box has a firewall that blocks the ping which is why the tracert ends there. I still can't connect -.-
"Privacy is dead, deal with it" - CEO Sun MicroSystems

Supanova

Finally got in touch with the server company and after about 30 minutes of them telling me it was my fault they went and found that the subnet mask was setup and that IDnet do something different from most mainstream ISP's which made me unable to connect.

Thanks to anyone that posted trying to help me. Regards.
"Privacy is dead, deal with it" - CEO Sun MicroSystems

Rik

Intriguing. Thanks for the feedback. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.