xboxscene.org forums

Author Topic: Port Check Failed  (Read 158 times)

CastorTroy

  • Archived User
  • Newbie
  • *
  • Posts: 3
Port Check Failed
« on: November 11, 2003, 03:27:00 PM »

Keep getting this same error, Im connecting my xbox using a crossover cable, Im using the latest version of Xlink.
I think my isp uses the inktmoi servers but I cant find any help on this subject,
Im not using a router or Hub. my firewall allows all connections for the xlink prog.
Anyone care to share knowledge
Logged

CastorTroy

  • Archived User
  • Newbie
  • *
  • Posts: 3
Port Check Failed
« Reply #1 on: November 11, 2003, 03:31:00 PM »

[01:17:44] X-Link configuration inspection begins..

[01:17:44] Attempting Socket Bindings..
[01:17:44] Attempting X-Link Data Stream Bind (34518 UDP)..
[01:17:44] Attempting X-Link Data Stream Bind (34518 UDP)..
[01:17:44] Attempting XBConnect Hosting Stream Bind (8602 UDP)..

[01:17:44] Attempting Port Loobpack Tests..

[01:17:45] Initialising WinPCap control layer..

[01:17:45] Enumerating WinPCap NICs:
[01:17:45] USB Cable Modem (MS's Packet Scheduler) - DeviceNPF_{5AE73897-B5F6-4066-8C7C-92F6FFBDF4C5}
[01:17:45] NETGEAR FA311 Fast Ethernet PCI Adapter (MS's Packet Scheduler) - DeviceNPF_{84FCD513-DF96-4E7D-89D1-A00A510C3D2F}

[01:17:45] Checking IsGood status of NICs:
[01:17:45] USB Cable Modem (MS's Packet Scheduler) =  1
[01:17:45] NETGEAR FA311 Fast Ethernet PCI Adapter (MS's Packet Scheduler) =  1

[01:17:45] Attempting Promiscuous Control:
[01:17:45] USB Cable Modem (MS's Packet Scheduler) - STARTED
[01:17:45] USB Cable Modem (MS's Packet Scheduler) - STOPPED
[01:17:45] NETGEAR FA311 Fast Ethernet PCI Adapter (MS's Packet Scheduler) - STARTED
[01:17:45] NETGEAR FA311 Fast Ethernet PCI Adapter (MS's Packet Scheduler) - STOPPED

[01:17:45] MAC Capturing:
[01:17:45] Listening 5 seconds on USB Cable Modem (MS's Packet Scheduler)
[01:17:50] Listening 5 seconds on NETGEAR FA311 Fast Ethernet PCI Adapter (MS's Packet Scheduler)
[01:17:51] 0050F2935A37->FFFFFFFFFFFF
[01:17:53] 34518 -> OK (192.168.0.1)
[01:17:53] 34519 -> OK (192.168.0.1)
[01:17:53] 8602 -> OK (192.168.0.1)
[01:17:53] 0050F2935A37->FFFFFFFFFFFF
[01:17:55] 0050F2935A37->FFFFFFFFFFFF

[01:17:55] UPnP Enumeration (WAIT):
[01:17:56] UPnP Init failed.. skipping enumeration..

[01:17:56] XServer External Test:
[01:17:56] Sending request..
[01:17:56] Waiting 5 seconds for reply..
[01:17:56] XServer accepted connection..
[01:17:56] Server -> Sent 3 test packets to 62.254.64.10 - HTTP response was 62.254.64.10 , full was

[01:18:01] Tests complete... post in the forum if you need to.
Logged

flat235

  • Archived User
  • Sr. Member
  • *
  • Posts: 292
Port Check Failed
« Reply #2 on: November 11, 2003, 03:38:00 PM »

OK.. Let me guess... UK, NTL user - yeah?

Well, they've apparently made an effort to stop u playing online games which u dont pay the gay extra money for... a few ppl, including Steg - the 3rd person ever to use XLink - have been blitzed by this...

Kai will fix it.. until then, please keep an eye out on here for an NTLUK fix... it *might* happen b4 Kai...

But sign up for the beta.. (pinned).. ppl with weird probs are just what I need there..

Thanks for your time so far,

TD
Logged

CastorTroy

  • Archived User
  • Newbie
  • *
  • Posts: 3
Port Check Failed
« Reply #3 on: November 11, 2003, 03:41:00 PM »

spot on NTL uk user good guess.

Ok so where do I go from here ........
How do i sign up for the BETA program ?
Logged

flat235

  • Archived User
  • Sr. Member
  • *
  • Posts: 292
Port Check Failed
« Reply #4 on: November 11, 2003, 03:49:00 PM »

Signup is here:

http://forums.xbox-scene.com/index.php?act...T&f=46&t=119606

I'm sorry about the NTL probs... it only actually emerged like 3 days ago... before then, it was all good.. Rest assured that everything is being done to get u guys back online - but we're fighting (i think) a concerted effort by NTL to block XLink's data ports... either way, Kai doesnt care about ports - so that will fix it either way... but an interim fix isnt out of the question..

TD
Logged

xmgr

  • Archived User
  • Newbie
  • *
  • Posts: 22
Port Check Failed
« Reply #5 on: December 09, 2003, 10:42:00 PM »

Thanks to rampantscot for helping me find this this thread.  

NTL are denying that they are blocking 34518 and 34519 on UDP.  (I called them Yesterday)

I realise that this is a short term problem as Kai will not be affected but I am *f*cking livid* with ntl for doing this.  

Can you please confirm that these are the ports that they would be blocking, and if there may be any others, before I fire off an email to TPTB.

Cheers,

--
xmgr.
Logged

xmgr

  • Archived User
  • Newbie
  • *
  • Posts: 22
Port Check Failed
« Reply #6 on: December 10, 2003, 12:35:00 AM »

Logged