Problems setting up proxy server

[dabean]

Let me explain the situation: 2 dsl connections - 1 at home, 1 at the office. Both Netgear DG834 firewall routers.

The theory is to use a capped account at home, and an uncapped (as in not capped yet) one at the office - with a proxy server installed for web browsing. That way I wouldn't have to swap accounts every time I wanted to browse, as I mainly use the net for gaming and local downloads from home.

Sounded simple enough until I tried it. I used NetProxy 4.0 because of the password protection (vital) and the fact that the trial version is complete but limited to one user (perfect). At the office everything works fine, I can connect to the proxy from any machine (using local ip), not from home though - standard IE "page cannot be displayed" error. Here's the setup:

Office DG834:
Router mode (bridge not supported) (192.168.0.1)
Incoming rule on the firewall for TCP port 8080 set to always allow, forward to proxy pc (192.168.0.2)
NAT enabled
DynDNS enabled and updating fine (triple checked)
Remote management disabled (also uses 8080)

Home 834: identical

NetProxy setup straight forward and works at the office, just added a rule to allow incoming connections from 165.165.0.0/16.
It's not an authentication problem as NetProxy has a system tray utility where you can enter your log-in details. I tried setting everything to use port 6500, same result. The port forwarding definately works on both ends (tested with p2p software)

I'm stumped. No, linux isn't an option due to the logistics involved.

Has any setup anyhing like this before? What am I missing?

Thanks

 

[stoke]

So - home pc's ie is setup to use office pc's proxy port 8080.
Home pc jumps request through home network, hits router, gets new ip address and localized port number, requests access to office outside ip address on 8080, office router routes request through to 192.168.0.2 8080 by creating a local ip addr for ther incoming request (NAT), then, the proxy on 192.168.0.2 has to send to your home computer the data. I think that this is where your problem lies. Is 8080 open for sending out on the office computer ? Does the office proxy allow sending to the NAT created ip address ?

Then - once you get this working - what stops me from using your office proxy ?

 

[dabean]

Yes, that's the idea.

8080 is open for sending, I think the problem is this...

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by stoke</i>
Does the office proxy allow sending to the NAT created ip address ?
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">


The proxy server does not allow anonymous connections, you have to supply a username and password.

I've tried googling for proxy servers that would work for me, but it seems our bandwidth situation is unique in the world.

 

[James]

Is the proxy set up to listen to local or everything. That was the problem I had a while ago

There is no peace without war!!!

 

[dabean]

I got it working!

One of those blonde moments, pains me to admit. Basically I use the office firewall to block internet access from a certain section of the network and had it misconfigured, overriding my port forwarding.

O well, thanks for the trouble people.