Strange 127.0.0.11 network problem

[The_real_dj]

Got a real strange problem at home on my xp machine, I am trying to connect to a remote access server at work. Its setup to map the ip address 127.0.0.11 to a server at work.
But for some reason on my xp machine all 127.0.0.* addresses go stright to local host. Example:
ping 127.0.0.15
Pinging 127.0.0.15 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

does anyone know why xp seems to be reverting all 127.0.0.* addresses to 127.0.0.1???

Cheers

[Xaccers]

That would be because 127.x.x.x is a loopback range you wally :pp

[The_real_dj]

thats what i thought but the coms guy at work said it would work and it does on windows 2000 but not on xp its really strange. ???

[The_real_dj]

actually can that lot, it looks like a problem with the nokia software that connects me to the server, its sayin cant bind to port!!!

sorry!!

[philip.j.fry]

Originally Posted by The_real_dj

actually can that lot, it looks like a problem with the nokia software that connects me to the server, its sayin cant bind to port!!!

sorry!!

Sounds like a firewall issue maybe, or you don't have permissions to set up a listening device.

Originally Posted by The_real_dj

thats what i thought but the coms guy at work said it would work and it does on windows 2000 but not on xp its really strange. ???

Sorry but it won't work on W2000 either - the only difference is that XP is slightly more intelligent - and whatever 127.x.x.x address you type in it will loop back and report it as 127.0.0.1 while W2K will loop back but still report it as the address you typed in.

[The_real_dj]

yea its a strang bit of kit, its called a nokia secure access server and some how it uses a java app loaded from a web browser to remap 127.0.0.* to servers at the other end. It works on my laptop fine but for some reason not my pc. It says something about unable to bind to socket, the only think i can think that is causing the problem is the latest IP V6 that i have instaled from windows update. But its a nokia problem not an ip problem as i origionally thought so on the blower to them in the morn, cheers though

[philip.j.fry]

Originally Posted by The_real_dj

yea its a strang bit of kit, its called a nokia secure access server and some how it uses a java app loaded from a web browser to remap 127.0.0.* to servers at the other end. It works on my laptop fine but for some reason not my pc. It says something about unable to bind to socket, the only think i can think that is causing the problem is the latest IP V6 that i have instaled from windows update. But its a nokia problem not an ip problem as i origionally thought so on the blower to them in the morn, cheers though

If you can post the exact java error, as well as the java error log if one is produced I can probably help you more, also is it an applet or a stand-alone app launched from java webstart?

[The_real_dj]

heres some screen shots of what i get:

aplet.jpg is the little port forwarding app that is loaded from the web site.
nokia.jpg is the page of the secure access server
log.jpg is the log from the java app

to be honest i dont think it is a java error as such, its probably just somthing with their app

Cheers anyway (i have had to remove any ips and user names)

So this software appears to try and forward traffic directed at 127.0.0.11:3389 to another, remote, server.

I think that this is relying on the fact that windows is treating 127.0.0.11 as a seperate ip address, even though it is actually still a loopback address.

It looks like this "feature" may have been removed (broken) in XP and any 127.x.x.x address is being converted to 127.0.0.1 - and therefore XP cannot bind to the 127.0.0.11 address.

I cannot ever imagine why Nokia would do it this way - but if I'm right then it will never work on XP.

[philip.j.fry]

Originally Posted by Pem

So this software appears to try and forward traffic directed at 127.0.0.11:3389 to another, remote, server.

I think that this is relying on the fact that windows is treating 127.0.0.11 as a seperate ip address, even though it is actually still a loopback address.

It looks like this "feature" may have been removed (broken) in XP and any 127.x.x.x address is being converted to 127.0.0.1 - and therefore XP cannot bind to the 127.0.0.11 address.

Yeah, actually it sounds like somebody typed one more 1 than was necessary, bit silly as theirs an easy way to get the localhost address in Java. The app in the first image they have incorrectly described as an applet but that doesn't matter really...just niggling

Things you could try are:

Make sure that you have no other services listening on port 3389,

If you're running a firewall, you might need to give the program access.

Try adding 127.0.0.1 to hosts, I can't remember whether this is acceptable or not for a windows hosts file (or if Java respects it):

127.0.0.1 127.0.0.11

[The_real_dj]

cheers phillip ive found out what it was!! My pc at home runs remote desktop on prot 3389 and so when the java app tries to bind to it it cant cause its already in use!. I have stopped this service and now all is ok

As for nokia ussing 127.0.0.11 rather than 127.0.0.1 its because we have a number of servers setup each one running on 127.0.0.*

Thanks for you help though