Cannot Connect To My Office Proxy - Opensuse 10.3

Hi all,
i'm newbie...
before post this...i have read this thread but i cant access the followed link

i have problem connect my opensuse with my office proxy. (in my office all pc and server use windows).
i want connect my laptop with opensuse 10.3 to internet. so, i can update my opensuse. i use my office proxy. i already set all value in yast - network service, but i still cannot update my opensuse.

when i want to test proxy setting, i always found error there

an error occurred during the HTTP proxy test.
curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information
sh: 4ckh0: command not found
sh: 3s: command not found

i think, opensuse refuse proxy authentication...
i believe i fill the right username and password there

when i use mozilla firefox. firefox accept the authentication.
i can post here

what should i do?

please help me to solve this problem.


here is my ipconfig detail in windows.

Windows IP Configuration

********Host Name . . . . . . . . . . . . : JKT01
********Primary Dns Suffix**. . . . . . . : xxx.co.id
********Node Type . . . . . . . . . . . . : Hybrid
********IP Routing Enabled. . . . . . . . : No
********WINS Proxy Enabled. . . . . . . . : No
********DNS Suffix Search List. . . . . . : xxxx.co.id
********************************************xxx.co.id
********************************************co.id

Ethernet adapter Local Area Connection:

********Connection-specific DNS Suffix**. : xxx.co.id
********Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
********Physical Address. . . . . . . . . : xx-11-25-6E-36-xx
********Dhcp Enabled. . . . . . . . . . . : Yes
********Autoconfiguration Enabled . . . . : Yes
********IP Address. . . . . . . . . . . . : 172.25.5.51
********Subnet Mask . . . . . . . . . . . : 255.255.255.0
********Default Gateway . . . . . . . . . : 172.25.5.29
********DHCP Server . . . . . . . . . . . : 172.25.4.1
********DNS Servers . . . . . . . . . . . : 172.25.5.22
********************************************172.28.1.1
********Primary WINS Server . . . . . . . : 172.25.5.22
********Lease Obtained. . . . . . . . . . : Saturday, May 31, 2008 5:18:51 PM
********Lease Expires . . . . . . . . . . : Tuesday, June 03, 2008 5:18:51 PM

Does your username or password contain a space, "
or $? I seem to remember there is a bug with the curl script where it doesn't quote it properly. I think it was fixed, but then you would have to be able to update to get the fix. You could try putting single quotes around it at the proxy dialog, as a workaround.

Does your username or password contain a space, "
or $? I seem to remember there is a bug with the curl script where it doesn't quote it properly. I think it was fixed, but then you would have to be able to update to get the fix. You could try putting single quotes around it at the proxy dialog, as a workaround.
[/b]

thanks for the reply...

there is no space or $ character in my username and password.
i use ! and | character in my password. is it bug too?

when i try to ping to my proxy in console, i have reply..

eastkidz@dkdaniel:~> ping 172.25.4.10
PING 172.25.4.10 (172.25.4.10) 56(84) bytes of data.
From 172.25.5.29: icmp_seq=1 Redirect Host(New nexthop: 172.25.5.253)
64 bytes from 172.25.4.10: icmp_seq=1 ttl=127 time=0.854 ms
64 bytes from 172.25.4.10: icmp_seq=2 ttl=127 time=0.268 ms
64 bytes from 172.25.4.10: icmp_seq=3 ttl=127 time=0.291 ms
64 bytes from 172.25.4.10: icmp_seq=4 ttl=127 time=0.286 ms

--- 172.25.4.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.268/0.424/0.854/0.249 ms
eastkidz@dkdaniel:~>

but...when i tried to ping any website...
there is no reply...

eastkidz@dkdaniel:~> ping www.google.com
PING www.l.google.com (64.233.189.99) 56(84) bytes of data.

--- www.l.google.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4016ms

eastkidz@dkdaniel:~>

Yes | is also a problem. Use single quotes around the password when entering in the proxy screen.

Yes | is also a problem. Use single quotes around the password when entering in the proxy screen.
[/b]

did you mean i should entering my pass like this?
sorry...i'm newbie
ex.
Yast - Network Services - proxy

Proxy Authentication
Username: daniel
password: '123!|45|!'

Yes.

It's just a workaround. The bug is in the way the password is presented to curl through the shell. That's why bits of your password appeared in the error message.

Yes.

It's just a workaround. The bug is in the way the password is presented to curl through the shell. That's why bits of your password appeared in the error message.
[/b]

well...
the problem still the same...

when i try to add repository... here is the error message..


i can browse to internet with mozilla and i can upload the foto, but still have the problem with opensuse update...

please give me advice to the next step


(maybe i'll take a rest first now is 6.12 am here...)
thanks...

That's a different error, you got past the password problem. You seem to have an extra / in front of opensuse path (the %2F), not sure why. Did you enter the update repository path yourself? Did you forget the http://? Do you have some extra spaces in it?

That's a different error, you got past the password problem. You seem to have an extra / in front of opensuse path (the %2F), not sure why. Did you enter the update repository path yourself? Did you forget the http://? Do you have some extra spaces in it?
[/b]

i really did not know about the problem full newbie
in my opninion, this is caused by unaccepted proxy authentication.
in other website, they say that i should change the config of /root/.curlrc
but..i still have the problem.


for more information.
my office use 2 domain and 2 proxy

xxxx.co.id -- proxy 172.25.4.10
and
xxx.co.id -- proxy 172.25.3.61

i work in xxxx division, but my desk in xxx division room. so, i connect in xxx network.
even in xxx network, but i can login to xxxx domain in windows


in opensuse.....is it difficult to config like that?

No, you were just unlucky you hit this bug.

Go have some rest and come back later and look at the problem.