UKONLINE ADSL

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi all,

i have ukonline service, on their website they state they run port blocking software
port blocking.

I want to remote admin into my computer, have forwarded ports 4899 through my BT modem, opened the port 4899 on Win Firewall, yet i cannot still connect from work.

With regards to my ip address, i am using dynds, where they tag your ip and convert it into a domain, whenever your ip changes, it updates automatically... so all you need to do is type in your given domain name...

Any ideas?

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

You have a misconfiguration somewhere. UKOL doesn't block port 4899, so either the port forwarding isn't working, or the firewall isn't configured correctly.

BT router modems can sometimes be a pig to get to work correctly away from the BT service. Usualy UKOL supplies an Actiontec modem - have you tried that?

Have you tried connecting to the IP rather than the name? ADSL IP allocations don't change *that* often.

Harry.

 

the reason i said they blocked the port is because it did work, i admin the computer from my mates house, the next day, i tried at work, but could not connect...

i tried pinging the computer from work and get 75% loss data...

 

This could be a firewall problem at work then.

Ths would be a separate issue. Can you get someone else to ping home from elsewhere to eliminate one possibility?

And if you do a traceroute at which hop do the packets dissapear?

Harry.

 

Traceroute???

my computer is off at moment, i'll try again tomorrow...

 

Investigating further - that port is used by Radmin.

I see that it can be set to only accept connections from specified IP addresses. While I'm sure you have thought about this, are you sure of the IP address at work that you appear to be connecting from?

Harry.

 

Traceroute is your friend! Like ping it checks out the lower layer connectivity.

Under Windows it is known as tracert

Harry.

 

Yes, this is Remote Adminstrator program, it is similar to Dameware and other "connect to my pc" programs.

Through RA, you can set it to recieve specific ip address or any, and/or set a password for incoming connections.

In my instance, i have not changed the port number nor have i set a password, once i have figured this problem, then i will set a password for incoming connections aswell as changing the port, hence computer turned off...

 

Tracing route to [my domain] [ip address]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms xx.xx.19.50
2 <10 ms <10 ms <10 ms xx.xx.255.150
3 xx.xx.255.150 reports: Destination host unreachable.

Trace complete.

Z:\>ping [my domain]

Pinging [my domain] [ip address] with 32 bytes of data:

Reply from xx.xxx.255.150: Destination host unreachable.
Reply from xx.xxx.255.150: Destination host unreachable.
Reply from xx.xxx.255.150: Destination host unreachable.
Reply from xx.xxx.255.150: Destination host unreachable.

Ping statistics for [ip address]:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Z:\>ping xx.xxx.255.150

Pinging xx.xxx.255.150 with 32 bytes of data:

Reply from xx.xxx.255.150: bytes=32 time<10ms TTL=254
Reply from xx.xxx.255.150: bytes=32 time<10ms TTL=254
Reply from xx.xxx.255.150: bytes=32 time<10ms TTL=254
Reply from xx.xxx.255.150: bytes=32 time<10ms TTL=254

Ping statistics for xx.xxx.255.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

- Sorry for the longest post, but that what shows up from work, i reckon it might be works firewall...

Any ideas???

 

if i ping me domain or my ip then the same error is occured.
Tracing route to [my domain] [ip address]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms xx.xx.19.50
2 <10 ms <10 ms <10 ms xx.xx.255.150
3 xx.xx.255.150 reports: Destination host unreachable.

Trace complete.

Z:\>ping [my domain]

Pinging [my domain] [ip address] with 32 bytes of data:

Reply from xx.xxx.255.150: Destination host unreachable.
Reply from xx.xxx.255.150: Destination host unreachable.
Reply from xx.xxx.255.150: Destination host unreachable.
Reply from xx.xxx.255.150: Destination host unreachable.

Ping statistics for [ip address]:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
--------------------------------------

confused? so am i!

 

My mate has just pinged my domain, with only 25% loss... this should now mean, that it is the firewall at work...

 

Hm - there are a number of things on those results that don't quite make sense to me.

What is xx.xx.255.150? This is where the trace stops, so something is blocking it.

This has got to be nearby, and not your machine. A machine on the end of an ADSL connection will have more than 10ms RTT.

I would say from the 3 items posted there that you have a firewall at work, and this firewall (or possibly a proxy) has the xx.xx.255.150 address.

From posting #12

Quite possibly - but there shouldn't be such loss either.

Harry.

 

Harry,

We do have a proxy at work...

...and do you have any idea of the 25% loss??

 

Hence the problems. See if the "powers that be" will allow a way though. You may have to tunnel over SSH or some similar scheme to keep them happy.

Do a traceroute to see where it is getting lost.

Harry.

 

seems like end of the tunnell as no way will they allow me to access my comp at home... no port opening, no access no nothing...

Cheers mate for all your help...

Appreciated...

 

50% there...

...so i sat down at my computer last night, started munching on my pringles, and thought "hmmm, whats wrong???". checked my port number - correct, checked port forwarding enabled on router - correct, checked if ports were open within xp firewall? NO!!!! that was the reason i couldnt connect, i quickly open the port and boom, was looping myself within remote admin using my domain!!! called my mate, same with him, able to connect, that was last night...

...today is a different day! try to connect at work, "cannot connect to server", thinking to my self, it must be works firewall, called my mate, he can not cannot either, yet he did connect last night???

... so my question is...

Is Windows XP SP2 Firewall adapative, or should i just turn it off and stick with my hardware firewall?

 

My advice would be to be use some different mechanism to connect to the PC in question. Try something like LogMeIn.

Set up an account with them, add the PC you want to control remotely and it will install a small client to that PC, then all you need is web access to get to your PC remotely.

eg, you goto the logmein website, enter your account details, then it shows any PC's that you installed the client to and are switched on. Click the remote control button and you are away. Seems to work well even in quite restricted environments.

 

I thought RDP used port 3389 ? Does on my system and port forwarding on it works a treat for me. Not sure about any others, but obviously it works. Strange.