Client can't get out thru Gateway

Mar 11 04 6:26 pm

Desktop runs Win98 (not SE) and is gateway as 192.168.01
Laptop runs XP Pro and is client as 192.168.0.2
Network works, files transfer all is well.
I install WinGate and nothing seems to change.
With GateKeeper running and Activity screen up when trying to access the internet I see a string of messages like:
DNS: A Lookup "microsoft.com" after a string of them it times out.
email produces the same sort of message:
DNS: A Lookup "mail.yahoo.com" and it too times out.

It seems I have something configured wrong and it appears to be on the gateway machine but I can't figure out what it is.

Any help appreciated,
Thanks,
Henry

Mar 11 04 8:24 pm

How do you connect to the internet and how is the gateway machine setup to obtain DNS, etc. ?

Mar 12 04 3:12 am

Pascal wrote:How do you connect to the internet and how is the gateway machine setup to obtain DNS, etc. ?

It's a DSL connection. I click on this icon which connects the gateway to the internet over the DSL line but even when I am online I can't see it on the client.

This got setup by a disk I got from Verizon. The line in produces a dial tone, but I don't know what the corresponding telephone number is.

Control Panel/Network/Configuration/TCP IP->PCI Ethernet Adapter/Properties shows-
DNS disable
Gateway blank

Henry

Mar 12 04 8:13 am

Does WinGate have a dial-up profile associated with that ?

Mar 12 04 2:27 pm

Does WinGate have a dial-up profile associated with that ?

Yes, it says--

General Tab
Host Name or IP Address is 1.1.1.1
Connect Using is iVasion PoET Adapter #1

Server Types Tab
Type of Dial Up Server is: PPP: Internet, Windows NT Server, Windows 98
no choices here

Advanced Options none checked, they are
log on to network
enable software compression
require encrypted password
require data encryption
record log file

Allowed Network Protocols
Only TCP/IP is checked
NetBEUI, IPX/SPX are not checked
[/quote]

Mar 12 04 3:15 pm

No, a corresponding profile in WinGate.

Mar 12 04 3:40 pm

Pascal wrote:No, a corresponding profile in WinGate.

Yes,
Right now it says Verizon Online connected

Properties
Enable this connection to be used by WinGate is checked
Username ok
password ok
domain is blank

If I disconnect and press dial the computer reconnects.

Henry

Mar 12 04 3:44 pm

Surfing from the server works fine, I assume. On the client, as you're using NAT from your description, ensure you have the gateway and DNS entries pointed to WinGate. Then, make sure the WinGate DNS Server is running (Not in a stopped state, from GateKeeper)

You can also try to add the ISP allocated DNS entries to the DNS/WINS Resolver (In GateKeeper)

Once you're connected and attempting to NAT, can you get a copy of the system route table for me, please ? (Route print from a command line)

The last thing to do is to check that your IP ranges are configured properly in the Advanced Settings (GateKeeper -> Options -> Advanced -> Network Interfaces) Your dial-up profile should be set to "Public/Untrusted" and your LAN card to "Private/Trusted".

Mar 12 04 4:48 pm

On the client, as you're using NAT from your description, ensure you have the gateway and DNS entries pointed to WinGate.

Not sure how to do this

WinGate DNS Server is running

is ok

add the ISP allocated DNS entries to the DNS/WINS Resolver

don't know how to find the ISP allocated DNS entries

get a copy of the system route

Active Routes:

Network Address Netmask Gateway Address Interface Metric
0.0.0.0 0.0.0.0 129.44.172.247 129.44.172.247 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
129.44.0.0 255.255.0.0 129.44.172.247 129.44.172.247 1
129.44.172.247 255.255.255.255 127.0.0.1 127.0.0.1 1
129.44.255.255 255.255.255.255 129.44.172.247 129.44.172.247 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 2
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 129.44.172.247 129.44.172.247 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
255.255.255.255 255.255.255.255 192.168.0.1 0.0.0.0 1

Your dial-up profile should be set to "Public/Untrusted" and your LAN card to "Private/Trusted".

It is

Henry

Mar 12 04 4:56 pm

You set the default gateway and dns servers in TCP/IP properties. So, on your XP client go to:

Start -> Control Panel -> Network Connections -> Local Area Connection (Could have a different name)

Click Properties

Find "Internet Protocol (TCP/IP)" and double click that.

Then check what is specified on the general tab.

You can find the ISP DNS servers by running (From the command prompt) ipconfig /all with the connection (Internet) established. It will return something like:

<snip>
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.190
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
<snip>

BTW. Does everything work fine from the server ?

Mar 12 04 6:10 pm

Internet on the gateway works fine. Interestingly, the
Wingate Dialup Monitor on the client says connected to Verizon Online
Status says connected for 38 minutes, bytes sent 21787, bytes received 0
when I click disconnect it disconnects the gateway computer. I then have to go back to the gateway and re-establish the internet connection which works fine. The Dialup Monitor on the client doesn't come up unless I reboot.

General tab says-
IP address 192.168.0.2
mask 255.255.255.0
Default Gateway 192.168.0.1
Preferred DNS Server 192.168.0.1

Ipconfig gives this--

Windows 98 IP Configuration

Host Name . . . . . . . . . : FATMAN

DNS Servers . . . . . . . . : 151.203.0.85

151.203.0.84

Node Type . . . . . . . . . : Broadcast

NetBIOS Scope ID. . . . . . :

IP Routing Enabled. . . . . : No

WINS Proxy Enabled. . . . . : No

NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.

Physical Address. . . . . . : 44-45-53-54-00-00

DHCP Enabled. . . . . . . . : Yes

IP Address. . . . . . . . . : 129.44.188.244

Subnet Mask . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . : 129.44.188.244

DHCP Server . . . . . . . . : 255.255.255.255

Primary WINS Server . . . . :

Secondary WINS Server . . . :

Lease Obtained. . . . . . . : 01 01 80 12:00:00 AM

Lease Expires . . . . . . . : 01 01 80 12:00:00 AM

1 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.

Physical Address. . . . . . : 44-45-53-54-00-01

DHCP Enabled. . . . . . . . : Yes

IP Address. . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . : 0.0.0.0

Default Gateway . . . . . . :

DHCP Server . . . . . . . . : 255.255.255.255

Primary WINS Server . . . . :

Secondary WINS Server . . . :

Lease Obtained. . . . . . . :

Lease Expires . . . . . . . :

2 Ethernet adapter :

Description . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet Adapter NDIS5 Driver

Physical Address. . . . . . : 00-04-5A-7D-06-62

DHCP Enabled. . . . . . . . : No

IP Address. . . . . . . . . : 192.168.0.1

Subnet Mask . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . :

Primary WINS Server . . . . :

Secondary WINS Server . . . :

Lease Obtained. . . . . . . :

Lease Expires . . . . . . . :

Still not sure which is the DNS of the ISP but I put 151.203.0.85 and 129.44.188.244 separately into the DNS/WNS Resolver and nothing happened.

Everytime I try to acces the internet on the client I can see the attempts rolling by on the activity screen of the gateway so it appears the client is communicating.

Mar 12 04 9:18 pm

was698002 wrote:Internet on the gateway works fine. Interestingly, the
Wingate Dialup Monitor on the client says connected to Verizon Online
Status says connected for 38 minutes, bytes sent 21787, bytes received 0
when I click disconnect it disconnects the gateway computer. I then have to go back to the gateway and re-establish the internet connection which works fine. The Dialup Monitor on the client doesn't come up unless I reboot.

WinGate Dialup Monitor. Are you using WGIC, rather than NAT ?

Mar 13 04 3:21 am

Duh!
I think I have both.
How do I get rid of either?

henry

Mar 13 04 11:22 am

After that I uninstalled from both computers and re-installed. Slightly better in that the client still can't get out, but when I start internet explorer on the client it actually opens a connection on the gateway but still cannot access it.

Henry