<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RH &amp;amp; Win2k Network Prob in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900403#M89040</link>
    <description>You are going to need some sort of IP network to connect your RH 8 to your Win2K system.  Either assigning an IP, etc. or using DHCP to assign one.  Samba runs over IP so to connect RH 8 to Win2K you will need IP.</description>
    <pubDate>Mon, 10 Feb 2003 22:21:08 GMT</pubDate>
    <dc:creator>Joe Knudsen</dc:creator>
    <dc:date>2003-02-10T22:21:08Z</dc:date>
    <item>
      <title>RH &amp; Win2k Network Prob</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900400#M89037</link>
      <description>I am brand new to Red Hat and am having some difficulty connecting to my Win2K system.&lt;BR /&gt;I have RH 8 and installed as server installing all packages. I also updated and installed all other packages.&lt;BR /&gt;Issue: my eth0 comes up as [failed] on startup unless I assign IP address and DNS even though I installed Samba and {think} it is setup properly. I prefer not assigning IP as opposed to letting Samba just link to Win2k. I am a newbie and need help!</description>
      <pubDate>Sun, 09 Feb 2003 19:11:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900400#M89037</guid>
      <dc:creator>Robert Washick</dc:creator>
      <dc:date>2003-02-09T19:11:58Z</dc:date>
    </item>
    <item>
      <title>Re: RH &amp; Win2k Network Prob</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900401#M89038</link>
      <description>In order to get an addressed assigned by dhcp, you have to contigure networking to actually do that.&lt;BR /&gt;&lt;BR /&gt;Pleae point the post if this is useful to you.&lt;BR /&gt;&lt;BR /&gt;As root user &lt;BR /&gt;&lt;BR /&gt;cd /etc/sysconfig/network/sripts&lt;BR /&gt;&lt;BR /&gt;vi(vi is a command line editor, you change things with it) a file called&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;ifcfg-eth0     &lt;BR /&gt;&lt;BR /&gt;From my red hat manual, to tell the configuration to get ip address from a dhcp server, add the following line...&lt;BR /&gt;&lt;BR /&gt;By default, a Red Hat client will not accept all information passed to it from the DHCP server.  The way the REd Hat Linux client handles DHCP server input is based on settings in the /etc/sysconfig/networkscripts/ifup script.   If the cient has DHCP turned on, when the system starts. &lt;BR /&gt;&lt;BR /&gt;In the file /etc/sysconfig/network you can have a line called DHCPCARGS&lt;BR /&gt;&lt;BR /&gt;If you have DHCPCARGS="-d" causes the ifup script to run in diagnostics to teh /var/log/messages file&lt;BR /&gt;&lt;BR /&gt;-B requestes a broadcast from a BHCP server&lt;BR /&gt;&lt;BR /&gt;-D forces that server to set the domain name of the Linux box.&lt;BR /&gt;&lt;BR /&gt;-H forces taht server to set the hostname of the linux box.&lt;BR /&gt;&lt;BR /&gt;Here is mine...&lt;BR /&gt;&lt;BR /&gt;DEVICE='eth0'&lt;BR /&gt;BOOTPROTO='none'&lt;BR /&gt;IPADDR='66.92.143.194'&lt;BR /&gt;NETMASK='255.255.255.224'&lt;BR /&gt;ONBOOT='yes'&lt;BR /&gt;GATEWAY='66.92.143.193'&lt;BR /&gt;TYPE='Ethernet'&lt;BR /&gt;USERCTL='no'&lt;BR /&gt;IPXPRIMARY_802_2="no"&lt;BR /&gt;IPXACTIVE_802_2="no"&lt;BR /&gt;IPXPRIMARY_802_3="no"&lt;BR /&gt;IPXACTIVE_802_3="no"&lt;BR /&gt;IPXPRIMARY_ETHERII="no"&lt;BR /&gt;IPXACTIVE_ETHERII="no"&lt;BR /&gt;IPXPRIMARY_SNAP="no"&lt;BR /&gt;IPXACTIVE_SNAP="no"&lt;BR /&gt;NETWORK='66.92.143.192'&lt;BR /&gt;BROADCAST='66.92.143.223'&lt;BR /&gt;HWADDR='00:c0:9f:08:2a:8c'&lt;BR /&gt;DHCP_HOSTNAME='investmenttool.com'&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;You might have a network compatability issue so here are some extra diags.&lt;BR /&gt;&lt;BR /&gt;Let me run you through some diagnotics.&lt;BR /&gt;&lt;BR /&gt;On the w2k box&lt;BR /&gt;&lt;BR /&gt;get a command prompt and type&lt;BR /&gt;ipfconfig&lt;BR /&gt;&lt;BR /&gt;hit enter.&lt;BR /&gt;&lt;BR /&gt;Let me know what it says.&lt;BR /&gt;&lt;BR /&gt;on the Red Hat box, as root user, open up a session and type &lt;BR /&gt;ifconfig&lt;BR /&gt;&lt;BR /&gt;hit enter.&lt;BR /&gt;&lt;BR /&gt;Let me know what you see there.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;from w2k ping (ip addy of red hat box)&lt;BR /&gt;&lt;BR /&gt;from redhat ping (ip addy of w2k box)&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 09 Feb 2003 21:17:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900401#M89038</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-02-09T21:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: RH &amp; Win2k Network Prob</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900402#M89039</link>
      <description>If I undrestand you well what you want is for your linux server to be a dhcp client&lt;BR /&gt;In order to do this you have to have a dhcp server and your linux setup as a client&lt;BR /&gt;Your linux server can be set as both at the same time (dhcp server and client)&lt;BR /&gt;or your dhcp linux client could point to a dhcp server on the lan (be it an ISP hookup using modem or whatever).&lt;BR /&gt;&lt;BR /&gt;in any case I find that using the command&lt;BR /&gt;&lt;BR /&gt;#setup &lt;BR /&gt;&lt;BR /&gt;is the easy way to go about it ... from there you can set up network&lt;BR /&gt;in a user friendly enviroment&lt;BR /&gt;&lt;BR /&gt;to stop and start your network once this done use &lt;BR /&gt;&lt;BR /&gt;/etc/init.d/network stop&lt;BR /&gt;/etc/init.d/network start&lt;BR /&gt;&lt;BR /&gt;you can also set it up the dhcp client by hand (editing and invoking scripts)&lt;BR /&gt;i any case I found it worth the time to read&lt;BR /&gt;man dhcpcd and the many howto.&lt;BR /&gt;&lt;BR /&gt;Probably that when you have solve your eth0 dhcp/client problem the samba/w2k hookup will be solved.&lt;BR /&gt;&lt;BR /&gt;hope this help &lt;BR /&gt;&lt;BR /&gt;Jean-Pierre Huc&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Feb 2003 09:54:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900402#M89039</guid>
      <dc:creator>Huc_1</dc:creator>
      <dc:date>2003-02-10T09:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: RH &amp; Win2k Network Prob</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900403#M89040</link>
      <description>You are going to need some sort of IP network to connect your RH 8 to your Win2K system.  Either assigning an IP, etc. or using DHCP to assign one.  Samba runs over IP so to connect RH 8 to Win2K you will need IP.</description>
      <pubDate>Mon, 10 Feb 2003 22:21:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rh-amp-win2k-network-prob/m-p/2900403#M89040</guid>
      <dc:creator>Joe Knudsen</dc:creator>
      <dc:date>2003-02-10T22:21:08Z</dc:date>
    </item>
  </channel>
</rss>

