Nokia Software Updater Cannot Connect

[Blindfiber]

Hello, i need some help with this problem i am facing.

I am using a client PC which is connected to the internet through a server that runs Wingate 6.2.0.1121. My OS is Windows XP SP2.

I have a Nokia phone which i wanted to update so i installed the Nokia Software Updater (NSU). When i run the application it gives me the following message:

"Network connection lost. Check your network connection or whether a firewall is preventing the application from working properly"

I installed NSU on the server and it connects. Kindly advise me how i can connect to the NSU network through a client PC.

[Blindfiber]

The application (NSU) is trying to connect to dsut.online.nokia.com

[Blindfiber]

CONNECT dsut-online-nokia-com:443 HTTP/1.0
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; NSL)
Host: dsut-online-nokia-com:443
Content-Length: 0
Proxy-Connection: Keep-Alive
Pragma: no-cache

The data sent represents a SSLv3-compatible ClientHello handshake.

[adrien]

Hi

That CONNECT command that's being sent is normally sent to a proxy server to tunnel a connection through to an end server. So the Nokia is configured to use WinGate as a proxy? Or is this being sent to the end server that the client is trying to connect to?

Many phones that get net connectivity through a PC install some sort of proxy software on the PC. Do you see any additional network adapters when the phone is plugged in?

Adrien

[Blindfiber]

Nokia Software Update is trying to esablish a connection with its site. Since the internet is routed through the server which runs wingate proxy server, i believe that some setting is prohibiting this connection.

I have tried using the software on the server and it connects to the site without any trouble.

Hence, there is no doubt in my mind that this has something to do with Wingate settings.

[adrien]

Hi

I think I understand now how it's set up.

I can't see anything with that request that should cause a problem with WinGate. Are you able to turn on debug logging in the WWW proxy and see what that indicates? Also if you turn on logging of session termination we should be able to see if the client or if it's the server that is disconnecting.

Adrien