Re: Demand-dial Interface and/or new Broadband connection?
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 24 Apr 2005 22:59:20 -0500
Is your server a domain controller?? If it is that will make a difference in
the way you configure dns. The link below explains more.
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382
I am confused in that you said you are using a router. Normally the router
will use the IP address that the ISP assigns and then use NAT/PAT to allow
multiple computer behind the router to have intenet access via a class C
network such as the 192.168.1.xxx as you mention. Yet your server route
table and Ipconfig results show that your server has the public IP address??
Your router needs to be connected to the DSL modem via the wan port on the
router and then your server and other computers should connect to the
"switch" ports on the router. If it has only one "lan" port then you need to
connect a hub or switch to the lan port to plug your other computers into.
Disable or delete the adapter [ maybe virtual pppoe??] that is using the
200.74.174.205 IP address on the server. Also try using tracert to establish
internet connectivity. Your pathping shows that the IP adresses 192.168.5.1
and 192.168.12.1 are in the path and those are "private" IP addresses yet
you are not indicating that you are using those network IP's?? --- Steve
XXXDSL modem ------ router WAN port-|XXX|-router LAN port --- your
computers.
"Jaime Stuardo" <JaimeStuardo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CCE7AB24-749D-4A71-A6A0-83157F1EDF16@xxxxxxxxxxxxxxxx
>I have done that and the only thing client could do was to resolve
>correctly
> the DNS.
>
> I have used finally these IP's:
>
> 1.- 192.168.1.1 : DSL router
> 2.- 192.168.1.2 : NIC that connects to the DSL router
> 3.- 192.168.1.3 : NIC that connects to the LAN
> 4.- 192.168.1.4 : A PC in the LAN named CAROLINA
> 5.- 192.168.1.5 : A PC in the LAN named JAIME
>
> This is the IPCONFIG information of a server (note that NIC with
> 192.168.1.2
> doesn't have default gateway. If I use 192.168.1.1 as its gateway, server
> cannot resolve names and therefore, cannot browse internet):
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : srv-dev
> Primary Dns Suffix . . . . . . . : DESYTEC.North
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : DESYTEC.North
>
> Ethernet adapter Internet:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : 00-11-43-2F-69-26
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.2
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter LAN:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : D-Link DFE-530TX PCI Fast Ethernet
> Adapte
> r (rev.C)
> Physical Address. . . . . . . . . : 00-0D-88-CA-8F-CC
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.3
>
> PPP adapter Manquehue:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 200.74.174.205
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 200.74.160.103
> 200.74.160.104
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> This is PathPing information of the server:
>
> Tracing route to www.microsoft.com.nsatc.net [207.46.199.120]
> over a maximum of 30 hops:
> 0 srv-dev.DESYTEC.North [200.74.174.205]
> 1 200.74.174.1
> 2 192.168.5.1
> 3 192.168.12.1
> 4 * * *
> Computing statistics for 100 seconds...
> Source to Here This Node/Link
> Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
> 0 srv-dev.DESYTEC.North
> [200.74.174.
> 205]
> 0/ 100 = 0% |
> 1 30ms 0/ 100 = 0% 0/ 100 = 0% 200.74.174.1
> 0/ 100 = 0% |
> 2 30ms 0/ 100 = 0% 0/ 100 = 0% 192.168.5.1
> 0/ 100 = 0% |
> 3 49ms 0/ 100 = 0% 0/ 100 = 0% 192.168.12.1
> 100/ 100 =100% |
> 4 --- 100/ 100 =100% 0/ 100 = 0% srv-dev.DESYTEC.North
> [0.0.0.0]
>
> Trace complete.
>
> And this is the ipconfig of JAIME client:
>
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : jaime
> Primary Dns Suffix . . . . . . . : DESYTEC.North
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : DESYTEC.North
>
> Ethernet adapter LAN:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet
> Adap
> ter
> Physical Address. . . . . . . . . : 00-0C-6E-2F-CF-F9
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.5
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.3
> DNS Servers . . . . . . . . . . . : 192.168.1.3
> Lease Obtained. . . . . . . . . . : Domingo, 24 de Abril de 2005
> 19:40:5
> 4
> Lease Expires . . . . . . . . . . : Lunes, 02 de Mayo de 2005
> 19:40:54
>
> And this is PathPing info of the JAIME client:
>
> Tracing route to www.microsoft.com.nsatc.net [207.46.20.60]
> over a maximum of 30 hops:
> 0 jaime.DESYTEC.North [192.168.1.5]
> 1 * * *
> Computing statistics for 25 seconds...
> Source to Here This Node/Link
> Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
> 0 jaime.DESYTEC.North
> [192.168.1.5]
>
> 100/ 100 =100% |
> 1 --- 100/ 100 =100% 0/ 100 = 0% jaime.DESYTEC.North [0.0.0.0]
>
> Trace complete.
>
>
> And finally this is the routing table of the server (note that the IP
> assigned by the ISP is 200.74.174.205 and the first entry in the routing
> table is created automatically when connection is established):
>
> IPv4 Route Table
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 11 43 2f 69 26 ...... Intel(R) PRO/1000 MT Network
> Connection
> 0x10004 ...00 0d 88 ca 8f cc ...... D-Link DFE-530TX PCI Fast Ethernet
> Adapter (
> rev.C)
> 0xc0005 ...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 200.74.174.205 200.74.174.205 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2 10
> 192.168.1.0 255.255.255.0 192.168.1.3 192.168.1.3 1
> 192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 10
> 192.168.1.3 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2 10
> 192.168.1.255 255.255.255.255 192.168.1.3 192.168.1.3 1
> 200.74.174.1 255.255.255.255 200.74.174.205 200.74.174.205 1
> 200.74.174.205 255.255.255.255 127.0.0.1 127.0.0.1 50
> 200.74.174.255 255.255.255.255 200.74.174.205 200.74.174.205 50
> 224.0.0.0 240.0.0.0 192.168.1.2 192.168.1.2 10
> 224.0.0.0 240.0.0.0 192.168.1.3 192.168.1.3 1
> 224.0.0.0 240.0.0.0 200.74.174.205 200.74.174.205 1
> 255.255.255.255 255.255.255.255 192.168.1.2 192.168.1.2 1
> 255.255.255.255 255.255.255.255 192.168.1.3 192.168.1.3 1
> 255.255.255.255 255.255.255.255 200.74.174.205 200.74.174.205 1
> Default Gateway: 200.74.174.205
> ===========================================================================
> Persistent Routes:
> None
>
> With this information, can you know why client computers can resolve DNS
> but
> cannot ping a site or even connect to it with browser? I was thinking that
> the problem may be concerning firewall, but I tested enabling HTTP port in
> 192.168.1.2 interface using private address 192.168.1.3, and event I
> disabled
> firewall but with the same results.
>
> Seeing Pathping information, I see that the packet doesn't even leave
> client
> computer. I don't know if I am interpreting it well.
>
> Thanks a lot
> Jaime
>
>
>
>
> "Steven L Umbach" wrote:
>
>> Well that makes more sense. 192.168.1.1 is the default gateway for your
>> network so any computer on the 192.168.1.xxx network needs to be
>> configured
>> with 192.168.1.1 as the default gateway if you want to access the
>> internet.
>> You could simply assign all your computers IP addresses on the
>> 192.168.1.x
>> network to access the internet which is what I do at home. The DSL router
>> will offer protection by blocking uninitiated inbound traffic into your
>> network in that it is a NAT/PAT device. You can double check that by
>> doing a
>> self scan at a site such as http://scan.sygatetech.com/ .
>>
>> If you still want to use RRAS to do NAT, then make sure that only the
>> network adapter with the IP of 192.168.1.2 is assigned the default
>> gateway.
>> That is what NAT will need to use as the "external" network interface per
>> instructions in the KB article I referred you to when you configure NAT.
>> You
>> don't need to do anything more than what is listed in that article to
>> configure NAT. As long as your "external" network adapter is enabled it
>> will
>> be an always on connection using DSL. It may help to disable RRAS and
>> start
>> all over with the wizard to set up your NAT connection.
>>
>> Another thing you should check is your network adapter priority order. In
>> network connections go to advanced/advanced settings and make sure that
>> the
>> network adapter for the "internal" network which would be 192.168.0.1 is
>> at
>> the top of the priority list. --- Steve
>>
>>
>> Jaime Stuardo" <JaimeStuardo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:8F2B540B-CE52-4781-9216-D283C0EF1EEA@xxxxxxxxxxxxxxxx
>> > Yes... I discovered yesterday that I have a DSL router. Its model is
>> > X8024r
>> > from Xavi Technologies. I knew that its assigned IP is 192.168.1.1 and
>> > it
>> > was
>> > supposed to be accesible by telnet or by a web interface as you said.
>> > Unfortunately, it seems that my ISP has changed the default password
>> > for
>> > it
>> > so I could connect to the administration interface :-(
>> >
>> > In order to connect to the DSL router, I had to assign the 192.168.1.2
>> > IP
>> > to
>> > the NIC that connects to it. So now both NIC's are in the same subnet,
>> > using
>> > netmask 255.255.255.0.
>> >
>> > Now that I know that this is not a modem but a router, how it is
>> > considered
>> > by RRAS? I think that for it it isn't a demand-dial interface then and
>> > in
>> > that case, I can connect using Network connections applet first and
>> > then,
>> > treat the connetion as it was always connected, am I right?
>> >
>> > So to have the picture clear. This configuration is if I had 3 NIC's?
>> > one
>> > for the LAN with IP 192.168.0.1, other intermediate with IP 192.168.1.2
>> > connected to the WAN through the gateway 192.168.1.1? If this were
>> > true, I
>> > thought if I configure 102.168.1.1 as the getway for interface
>> > 192.168.1.2
>> > it
>> > would work, but it didn't.
>> >
>> > Do you know how to manage this case?
>> >
>> > Thanks a lot in advance
>> > Jaime
>> >
>> >
>> > "Steven L Umbach" wrote:
>> >
>> >> Modems do not get IP addresses, they are the interface between the
>> >> telephone
>> >> line and your Ethernet network. A DSL router device would need an IP
>> >> address
>> >> from your ISP and you can manage them through a web interface. Maybe
>> >> you
>> >> have one of those? --- Steve
>> >>
>> >>
>> >> "Jaime Stuardo" <JaimeStuardo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> message
>> >> news:8AE48862-06EF-4ECA-8D44-AA01CD3F3CCE@xxxxxxxxxxxxxxxx
>> >> > You mean that the external adapter should have the IP assigned by
>> >> > the
>> >> > ISP?
>> >> >
>> >> > In my case, the modem gets the IP... the external adapter remains
>> >> > with
>> >> > an
>> >> > IP
>> >> > I have to manually assign.
>> >> >
>> >> > "Steven L Umbach" wrote:
>> >> >
>> >> >> Your external adapter would be the one that is connected to the
>> >> >> internet/ADSL modem. If that adapter connects to your ADSL modem
>> >> >> then
>> >> >> it
>> >> >> should have the IP address that your ISP assigns either through
>> >> >> static
>> >> >> IP
>> >> >> address or dynamic IP address. I have not used DSL in a while but
>> >> >> if I
>> >> >> remember correctly I have to use a pppoe "connectoid" unlike my
>> >> >> cable
>> >> >> modem
>> >> >> where I do not have to do that anymore. NAT just needs to know the
>> >> >> external
>> >> >> adapter because that is the only one that will contain the default
>> >> >> gateway
>> >> >> and that would be the adapter that is configured with the pppoe
>> >> >> onnectoid. --- Steve
>> >> >>
>> >> >>
>> >> >> "Jaime Stuardo" <JaimeStuardo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> >> message
>> >> >> news:318BB99A-64D3-436E-8E84-B2F64E483D16@xxxxxxxxxxxxxxxx
>> >> >> > Hi Steven,
>> >> >> >
>> >> >> > That step by step guide talks about the external interface yo
>> >> >> > have
>> >> >> > the
>> >> >> > addresses provided by the ISP, but that isn't my configuration.
>> >> >> > That
>> >> >> > external
>> >> >> > interface is connected to the ADSL modem and it is really
>> >> >> > assigned
>> >> >> > IP
>> >> >> > from
>> >> >> > the ISP. The external NIC remains without IP address until I
>> >> >> > assign
>> >> >> > to
>> >> >> > it
>> >> >> > a
>> >> >> > static one.
>> >> >> >
>> >> >> > When you say that I should create a network connection for NAT,
>> >> >> > do
>> >> >> > you
>> >> >> > mean
>> >> >> > that I have to create it only in RRAS MMC? I have to delete the
>> >> >> > network
>> >> >> > connection I created in control panel?
>> >> >> >
>> >> >> > Thanks
>> >> >> > Jaime
>> >> >> >
>> >> >> > "Steven L Umbach" wrote:
>> >> >> >
>> >> >> >> Review the article in the link below from Microsoft on how to
>> >> >> >> configure
>> >> >> >> NAT
>> >> >> >> and make sure you select the proper network adapter for external
>> >> >> >> that
>> >> >> >> is
>> >> >> >> connected to the internet. You should only have to create the
>> >> >> >> network
>> >> >> >> connections in "network connections" for NAT . I have used DSL
>> >> >> >> in
>> >> >> >> the
>> >> >> >> past
>> >> >> >> and the pppoe connectoid is a pain. You might want to bypass it
>> >> >> >> and
>> >> >> >> use a
>> >> >> >> NAT router/firewall instead that connects to your DSL modem.
>> >> >> >> These
>> >> >> >> devices
>> >> >> >> will have different capabilities and costs depending on your
>> >> >> >> needs.
>> >> >> >> The
>> >> >> >> Netgear ProSafe line starts at well under $100. --- Steve
>> >> >> >>
>> >> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;816581
>> >> >> >>
>> >> >> >> "Jaime Stuardo" <JaimeStuardo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> >> >> >> in
>> >> >> >> message
>> >> >> >> news:D142200F-FB94-4053-9C39-5EC7542AB7AF@xxxxxxxxxxxxxxxx
>> >> >> >> > Hi all...
>> >> >> >> >
>> >> >> >> > I'm getting problems configuring NAT so that LAN clients can
>> >> >> >> > connect
>> >> >> >> > to
>> >> >> >> > Internet through the Windows Server 2003 machine.
>> >> >> >> >
>> >> >> >> > I know that I have to create a demand-dial interface in RRAS
>> >> >> >> > MMC
>> >> >> >> > since
>> >> >> >> > Server connects to Internet through a DSL modem. But, what
>> >> >> >> > about
>> >> >> >> > if
>> >> >> >> > I
>> >> >> >> > create
>> >> >> >> > a new broadband connection in Network Connections of control
>> >> >> >> > panel?
>> >> >> >> > This
>> >> >> >> > latter alwats work when I connect to Internet from the server.
>> >> >> >> > When
>> >> >> >> > I
>> >> >> >> > only
>> >> >> >> > create a demand dial interface in RRAS, it never connects.
>> >> >> >> >
>> >> >> >> > How can I do it?
>> >> >> >> > Thanks a lot in advance
>> >> >> >> >
>> >> >> >> > Jaime
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
.
- Follow-Ups:
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Jaime Stuardo
- Re: Demand-dial Interface and/or new Broadband connection?
- References:
- RRAS: Demand-dial Interface and/or new Broadband connection?
- From: Jaime Stuardo
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Steven L Umbach
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Jaime Stuardo
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Steven L Umbach
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Jaime Stuardo
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Steven L Umbach
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Jaime Stuardo
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Steven L Umbach
- Re: Demand-dial Interface and/or new Broadband connection?
- From: Jaime Stuardo
- RRAS: Demand-dial Interface and/or new Broadband connection?
- Prev by Date: Client on Win95 can't login
- Next by Date: Re: netsh problem
- Previous by thread: Re: Demand-dial Interface and/or new Broadband connection?
- Next by thread: Re: Demand-dial Interface and/or new Broadband connection?
- Index(es):
Relevant Pages
|
Loading