| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: Member-to-Member Support [Read Only]
Thread: More proxy help (please) :-( |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 24
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ok so I've been reading over the previous threads and have checked over the support area as well so I decided to post here.
I'm trying to get the agent to connect using some of the computers at work. All of the machine go through a proxy, so I figured I would check the settings using Internet Explorer. Found that the address was http://samm-sbs and the port was 8080. So, I entered this information into the WCG proxy configure and tried to connect and no luck. So then I figured I may need a login for it, so I snuck an admin login/pass and entered them and still no luck. The errors I have been getting are the proxy, network admin errors. So, in order to check my setting I went downstairs to the computers that have the internet disabled, checked the IE settings to discover that tthey simply didn't have proxy settings set. I entered the address and the port and hit refresh, then it asked for a login/pw which I entered the one I found and sure enough the page loaded for me. So if these settings AND login/pw work for using IE, then why won't they work for WCG? Unfortunately I do not have access to the firewall, nor will they be willing to allow me access. I also don't have the option of asking the tech since he is really never there, maybe once every 2 months at night. I was reading that ports 80 and 443 need to be open, so I thought maybe this is the problem? But if it's running through a proxy then those ports probably aren't going to be open anyways are they? Will those ports be automatically forwarded through the proxy port of 8080 from the settings I give the agent? Are there any tests I can run on the computer(s) to see what is going on? My account allowed me admin actions such as registry edit and whatnot, I just don't have firewall access. Another concern is that the proxy address doesn't seem to be a complete one, even though it does work for IE. When I enter the proxy address (http://samm-sbs) the agent warns me that it appears to be an incomplete address. Anyone have any ideas/comments? I'll be back tomorrow afternoon af work to run any tests and whatnot. Even if I need to use a program to configure or test I am willing to do so. Thanks, |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have posted a query about your post, since I cannot help.
mycrofth |
||
|
|
nerd01
Cruncher Joined: Mar 19, 2005 Post Count: 41 Status: Offline |
The address you have posted looks weird... If it works for IE maybe try to ping it and learn it's IP, so you could use it with WCG agent.
----------------------------------------Good luck! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The address you have posted looks weird... If it works for IE maybe try to ping it and learn it's IP, so you could use it with WCG agent. Good luck! Thanks for the tip, i will do that. I'm also thinking it may have something to do with anti-virus software? I'm going to have to double check, but i think each client computer may be running it's own software protection.. not sure if they're also firewalls or just antivirus |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The address you have posted looks weird... If it works for IE maybe try to ping it and learn it's IP, so you could use it with WCG agent. Good luck! Ok I tried again today. I pinged the proxy address (http://samm-sbs) through command and it did infact ping. I also tried entering the direct IP that was brought up my command prompt but still no go. It also gave me a more elaborate address of samm-sbs.sammclub.dom (yes, .dom). Tried that, and no go. Is there any way to test pinging through specific ports? I would like to just be able to see if I can send anything through the port at all. Like I say, IE works just fine with those settings so I just don't get it. What could be configured on the firewall that would allow IE to work through the proxy but not WCG? I guess I don't quite understand how the proxy works. WCG originally needs ports 80 and 443 to be open, but if you're going through a proxy this is not true right? because they're being forwarded through the proxy port. Does it make a difference as to what the original ports are that are being requested to pass through the proxy? For example, is it possible that the proxy allows the request of port 80 to pass through but not port 443 to pass even though they all eventually go through the proxy specific port (8080 in my case), or are they all the same? Are there any more pings/tests/configuring I could try in order to get to the bottom of this whether it will work or not? Thanks for the help guys. [Edit 1 times, last edit by Former Member at Apr 23, 2005 8:56:29 AM] |
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges: 
|
Try leaving the "http://" part off of the address. You might try using the numeric form of the address instead (nnn.nnn.nnn.nnn) which you can get with the ping command or host command, if they work and available on your system. Use the same port (and address) specified in the IE setting at (Tools-> Internet Options-> Connections-> LAN Settings -> Proxy sever).
The proxy port number has nothing to do with port 443 used by the agent. The proxy handles all ports and addresses and ports you might want to use and feeds them through the proxy address/port to the proxy server which converts them back to normal address/ports for accessing the Internet. If you can browse with that proxy setting to the open Internet, the agent should work with those settings also. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Try leaving the "http://" part off of the address. You might try using the numeric form of the address instead (nnn.nnn.nnn.nnn) which you can get with the ping command or host command, if they work and available on your system. Use the same port (and address) specified in the IE setting at (Tools-> Internet Options-> Connections-> LAN Settings -> Proxy sever). The proxy port number has nothing to do with port 443 used by the agent. The proxy handles all ports and addresses and ports you might want to use and feeds them through the proxy address/port to the proxy server which converts them back to normal address/ports for accessing the Internet. If you can browse with that proxy setting to the open Internet, the agent should work with those settings also. I tried both the actual address of the proxy that I pinged, as well as leaving the http:// part off. I also have been entering the port and address that I found in my IE settings.  I'm a little frustrated by this. Doesn't IE just use port 80? Does this mean that port 80 could be open for IE but port 443 might be closed causing WCG to not be able to connect? Could the port be closed on the physical computer, or would it more likely be a firewall thing blocking port 443 from going through? Maybe I could use some sort of port sniffer? |
||
|
|
nerd01
Cruncher Joined: Mar 19, 2005 Post Count: 41 Status: Offline |
Well, I'm afraid it's possible that a firewall on the proxy can block outbound connections on some ports....
---------------------------------------- I'll check back with you later and try to help you to see if that's really the problem. Regards, |
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges:
|
Firewalls, spyware blockers, and virus scanners can sometimes block communications as well. Do you have any of these installed and which versions? Try disabling them to see if that helps. If these tools log what they are blocking, you could check there to see if they are causing the problem. https://... secure web site accesses use port 443, so that would be another thing to check with your browser.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Firewalls, spyware blockers, and virus scanners can sometimes block communications as well. Do you have any of these installed and which versions? Try disabling them to see if that helps. If these tools log what they are blocking, you could check there to see if they are causing the problem. https://... secure web site accesses use port 443, so that would be another thing to check with your browser. can you give me an example of a site to check this with? actually, when i load this forum it gives me a secure warning, would this work? the computer is running a virus scanner, i think its mcafee but i will have to double check |
||
|
|
|