Win2K proxy setup

[Guest_imported]

Hello,

After reading through the forums, I have managed to solve a few of my problems....good site guys!

However, I am still left with a small niggle.

Environment : Gateway PC (Win2K Pro) running winproxy to share the connection with another Win2k Pro system. Both network cards have been assigned class C ip's and masks. I have installed a loopback adapter on the gateway machine so that I can run some apps and servers that require a fixed internal ip. Winproxy 'was' bound to both the loopback IP and the Network card IP (Multiple IP setup).

Gateway NIC IP : 192.168.1.10
Gateway Loopback : 192.168.1.2
Networked NIC IP : 192.168.1.11

Here is the problem.....

If both system are running, then there is no problem, all works fine, however.....as soon as the networked system is removed from the network (switched off, or unplugged) then the network configuration changes. Obviously, the network card IP is lost from the configuration of winproxy (why does Win2K do this?) and so winproxy requires confirmation that the loopback IP is still available. I have to tell it to use the loopback IP again, even tho it was included in the original configuration.

What I need to know is this :

1. Is there anyway of keeping the network card active, even if the networked pc is not "alive" and the LAN is "down" ?

2. Is there any proxy available (must support socks) that can keep a configuration even if the IP of the network card on the gateway is unavailable ?
If it can hold the configuration for 192.168.1.10, and just ignore the fact that it is not available, then, maybe it could recognise that as soon as the networked pc comes "alive" then it can route the connection.

I am happy to use the Loopback adpter for the local applications, but obviously I cannot point the networked PC to use the proxy running on the loopback adapter IP, because that particular adapter cannot be seen accross the network.

Really, I need the network IP to remain held in a configuration for a proxy (available or not), or constantly available (thus eliminating the need for the loopback adapter).

Am I making any sense here? I hope so.....

Any thoughts?

Kind Regards

Onslo

 

[sixthsense]

install ms proxy 2.0
all your probs will be solved
but u require either nt server or win2k server for that
for win2k server there is a patch avalaible on microsoft site to install ms proxy 2.0 get it first.
Kapil Technical Director
Infovalley Interwebspiders Pvt. Ltd.
Microsoft Certified System Engineer
visit

http://www.interwebspiders.com

If u find the information provided here useful to u then let me know by clicking on the link below s-)

 

[Guest_imported]

Many Thanks,

Does this mean that I will have to aquire another new OS? or is there an upgrade to Win2K server available?

The reason that I am asking is because I don't really want to have to purchase a new operating system. Windows 98 never had the problem, but was not stable enough to cope with what I required from it. Win2K pro seemed the way to go, and from good experience with a non-server system, I decided that I could install it as my server OS and it should resolve the stability issues that I had with 98. This does not seem to be the case.

Many thanks for your response....

Onslo

 

[Guest_imported]

I have managed to get it working now (still using Win2K Pro).

Wnproxy 4.0 R1c was the answer. It install the WANS Miniport Deterministic Network Enhancer (Netbeui protocol) which seems able to update the Winproxy config file on the fly. The newer version of Winproxy also seems able to remember it's original configuration and not lose it's original settings if any network changes occur.

Much better!

Onslo