ICS / (DNS?) Problem with Sharing Client

T

Tad Ashlock

Hello Everybody,

I'm having a problem with ICS on Windows 2000 Pro. It's *almost*
working, but I can't get the sharing client to access a DNS (I
think). I've tried following the online help and searching Google
Groups, but I haven't found anything that solves my problem.

Here's the scenario:

I use a 56k dial-up connection to my ISP on the ICS host. I have an
ethernet connection between the ICS host and the ICS client. I can
establish the dial-up connection and the host can fully access the
internet. The ICS host and the ICS client (both Win2k Pro) can see
each other through the Windows Network (via My Network Places). The
ICS client can ping an IP address on the internet and get responses,
but it can't ping a site by name.

For example, I try to ping Google from the ICS client:

============================================================
C:\>ping 66.102.7.147

Pinging 66.102.7.147 with 32 bytes of data:

Reply from 66.102.7.147: bytes=32 time=187ms TTL=238
Reply from 66.102.7.147: bytes=32 time=156ms TTL=238
Reply from 66.102.7.147: bytes=32 time=172ms TTL=238
Reply from 66.102.7.147: bytes=32 time=172ms TTL=238

Ping statistics for 66.102.7.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 187ms, Average = 171ms

C:\>ping www.google.com
Unknown host www.google.com.
============================================================

So I tried to use the IP address in IE (http://66.102.7.147/), but it
timed out with with the usual "The page cannot be displayed" and
"Cannot find server or DNS Error" at the bottom.

Anybody want to try tackling this one? I've included dumps from
ipconfig, route, and tracert for both the host and the client below.

Thanks,

Tad Ashlock <[email protected]>



ICS Host (Windows 2000 Pro SP4):

Before establishing dial-up connection:
============================================================
C:\Home>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : arrakis
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21041 Based PCI Ethernet Adapter
Physical Address. . . . . . . . . : 00-C0-F0-38-0F-BB
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

C:\Home>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x3000003 ...00 c0 f0 38 0f bb ...... Intel DC21041 PCI Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
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 192.168.0.1 192.168.0.1 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
===========================================================================
Persistent Routes:
None
============================================================


After establishing dial-up connection:
============================================================
C:\Home>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : arrakis
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21041 Based PCI Ethernet Adapter
Physical Address. . . . . . . . . : 00-C0-F0-38-0F-BB
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

PPP adapter ZiaNet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 216.31.22.175
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 216.31.22.175
DNS Servers . . . . . . . . . . . : 216.234.192.92
216.234.213.130

C:\Home>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x3000003 ...00 c0 f0 38 0f bb ...... Intel DC21041 PCI Ethernet Adapter
0x9000004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 216.31.22.175 216.31.22.175 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 1
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
216.31.22.1 255.255.255.255 216.31.22.175 216.31.22.175 1
216.31.22.175 255.255.255.255 127.0.0.1 127.0.0.1 1
216.31.22.255 255.255.255.255 216.31.22.175 216.31.22.175 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 216.31.22.175 216.31.22.175 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 216.31.22.175
===========================================================================
Persistent Routes:
None

C:\Home>tracert 66.102.7.147

Tracing route to 66.102.7.147 over a maximum of 30 hops

1 120 ms 110 ms 130 ms 216-31-22-1.zianet.com [216.31.22.1]
2 130 ms 120 ms 120 ms abq-router-02.zianet.com [216.234.212.18]
3 120 ms 130 ms 120 ms 12.125.99.97
4 121 ms 130 ms 120 ms gbr2-p70.phmaz.ip.att.net [12.123.142.50]
5 161 ms 430 ms 150 ms tbr2-p013402.dlstx.ip.att.net [12.122.10.81]
6 140 ms 140 ms 141 ms ggr2-p390.dlstx.ip.att.net [12.123.17.85]
7 150 ms 141 ms 150 ms att-gw.dfw.level3.net [192.205.32.114]
8 161 ms 150 ms 160 ms so-1-2-0.bbr2.Dallas1.Level3.net [209.244.15.165]
9 150 ms 160 ms 170 ms ge-0-1-0.bbr1.SanJose1.Level3.net [64.159.1.129]
10 150 ms 170 ms 160 ms ge-6-0.ipcolo2.SanJose1.Level3.net [64.159.2.4]
11 170 ms 160 ms 171 ms unknown.Level3.net [209.247.202.218]
12 170 ms 171 ms 190 ms 216.239.47.146
13 170 ms 180 ms 171 ms 216.239.49.142
14 181 ms 180 ms 180 ms 66.102.7.147

Trace complete.
============================================================


ICS Client (Windows 2000 Pro SP4):
============================================================
C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : caladan
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21041 Based PCI Ethernet Adapter #2
Physical Address. . . . . . . . . : 00-C0-F0-37-1E-E8
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 c0 f0 37 1e e8 ...... Intel DC21041 PCI Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 1
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 1
224.0.0.0 224.0.0.0 192.168.0.2 192.168.0.2 1
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

C:\>tracert -d 66.102.7.147

Tracing route to 66.102.7.147 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
[snip]
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
============================================================
 
A

Ace Fekay [MVP]

In
Tad Ashlock said:
Hello Everybody,

I'm having a problem with ICS on Windows 2000 Pro. It's *almost*
working, but I can't get the sharing client to access a DNS (I
think). I've tried following the online help and searching Google
Groups, but I haven't found anything that solves my problem.

Here's the scenario:

I use a 56k dial-up connection to my ISP on the ICS host. I have an
ethernet connection between the ICS host and the ICS client. I can
establish the dial-up connection and the host can fully access the
internet. The ICS host and the ICS client (both Win2k Pro) can see
each other through the Windows Network (via My Network Places). The
ICS client can ping an IP address on the internet and get responses,
but it can't ping a site by name.
<snip>

Are you getting any errors in the event log of the client or the ICS
machine?

Are there any services disabled on the client or the ICS machine?

On the client, if you manually set the DNS address (easily done in IP
properties) to 4.2.2.2, does it then work?

Just a note on IP addresses in the browser, that doesn't necessarily mean it
will work using an IP because many sites use the host header (the URL) as a
website identifier in the webserver.

This could also be an MTU issue (not saying it is and MTU issues usually are
ADSL based but you have dialup). See the first link on how to determine if
it is. Other links are more info on the MTU and what it is.

MTU - How to test and how to set in registry:
http://gw.renner.bei.t-online.de/windowsxp/mtu.htm

Troubleshooting MTU Size in PPPoE Dialin Connectivity-ADSL - Cisco
http://www.cisco.com/en/US/tech/tk175/tk15/technologies_tech_note09186a0080093bc7.shtml

Optimal MTU configuration for PPPoE ASDL Connections:
http://www.mynetwatchman.com/kb/ADSL/pppoemtu.htm

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top