Problems with Win XP Server and Win 98 Client

[Robzilla]

I have my network currently set up this way...

CABLE MODEM <----> Host/Server Computer WinXP <---Crossover Cable---> Client Computer Win98

Right now my problem is thus:

The client computer does not recognized the Wingate Server at all.

The Client computer can access and see the host computer over the network and vice versa.

Any helpwould be greatly appreciated.

[Pascal]

Which machine did you start first? Also, which version of WinGate are you running?

(If you're running 6.0 you should be fine, because dynamic binding means WinGate will rebind when the adapter becomes available)

How does the client connect through the WinGate server? Are you using proxies / NAT / WGIC ?

[Robzilla]

I am using Wingate 5.2.3 and I start the server first

The client connections via crossover cable to the server machine using WGIC.

[Pascal]

Can you see the server in the WinGate Internet Client Control Panel ? (Has it been discovered by GDP, in other words).

If you can, try manually selecting it. Otherwise, add it explicitly.

[Robzilla]

I added it however it still doesn't recognize it and cannot connect to it.

[Pascal]

Alright. Can you post the ip addresses you are using on both machines here, please?

Then, if you setup a proxy in your client (Point Internet Explorer to the internal IP of your Server) - can you establish a connection? I know this overrides WGIC, but the idea is to see if it works.

Then, also remember that you should set a DNS Server for the client - which can be the internal IP of WinGate (If you're running WinGate's DNS Server)

[Robzilla]

Alright,

My Server machine is using 2 NICs.
The First NIC is 68.9.*.* (assign by ISP)
The second NIC is 192.168.0.1

The Client Machine has one.
192.168.0.2

I've set the DNS and IE to the internal address of the Server.

So far nothing has happened.

[Pascal]

Sorry, I just re-read all the posts. The server starts first. In that case, the adapter that points to the client would be in a state of "Cable unplugged" until the client starts up, correct? (Or something similar).

Try stopping the Engine and then starting it again. WinGate can only bind to an adapter if it sees it when it starts, and on XP it would start as a service (During bootup) which is way before the adapter theoretically becomes available (When the client has started).

If you have a 5.x license, you can upgrade to 6.0 for free. (Depending on when you purchased you might not get all the new 6.0 functionality). 6.0 has dynamic bindings, which uses a policy based approach to automatically bind as adapters become available. (In part to fix this type of problem)

[Robzilla]

I just upgraded to version 6 and everyitng works =/

Thanks for the help.