Koozali.org: home of the SME Server

Ethernet woes

Dan Brown

Re: Ethernet woes
« Reply #30 on: April 16, 2003, 09:05:48 PM »
Ray Mitchell wrote:

> If you want your workstations to be able to talk to the
> server then the w/s and server must ALL have the IP address
> in the correct range.
> One of your w/s (persius I think it was) has an IP of
> 192.168.40.10 whereas it needs to be in the range
> 192.168.40.65 to 192.168.40.250 which your sme DHCP server is
> providing to the network.. This should happen automatically
> if you set everything up correctly (as advised).

Sorry, Ray, this is not correct.  You're right that the IP address needs to be in the correct range, but the "correct range" is his class C subnet--in this case, 192.168.40.[1-254].  If he's manually setting the IP addresses on his client machines, as he appears to be, those addresses must _not_ be within the DHCP range--so, in this case, any manually-set addresses must be 192.168.40.[1-64].

Of course, if he just has the client machines obtain the IP adress automatically via DHCP, they'll get an address in the correct range, along with all the other information they need to operate correctly.

rhys

Re: Ethernet woes
« Reply #31 on: April 17, 2003, 05:27:01 AM »
Ok. I deleted everything from Network Neighbourhood and reinstalled the drivers. Now there's just the ethernet adaptor plus TCP/IP. For some bizarre reason, it kept complaining that "your network is not complete" until I'd added Client for Microsoft Networks". The I/P config is now:
   (C)Copyright Microsoft Corp 1981-1998.

C:\AWKWARD>ipconfig -all

Windows 98 IP Configuration

        Host Name . . . . . . . . . : PERSIUS
        DNS Servers . . . . . . . . : 195.92.195.95
                                      195.92.195.94
        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. . . . . . . . . : 217.134.34.227
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . : 217.134.34.227
        DHCP Server . . . . . . . . : 255.255.255.255
        Primary WINS Server . . . . :
        Secondary WINS Server . . . :
        Lease Obtained. . . . . . . : 01 01 80 00:00:00
        Lease Expires . . . . . . . : 01 01 80 00:00:00

1 Ethernet adapter :

        Description . . . . . . . . : 3Com EtherLink PCI
        Physical Address. . . . . . : 00-50-04-36-AB-00
        DHCP Enabled. . . . . . . . : No
        IP Address. . . . . . . . . : 192.168.40.10
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . : 192.168.40.1
        Primary WINS Server . . . . :
        Secondary WINS Server . . . :
        Lease Obtained. . . . . . . :
        Lease Expires . . . . . . . :

I'll try to connect to Zeus later. Right now I'm just doing a satisfactory test - does it still dial-up - it does.

Rhys

Ray Mitchell

Re: Ethernet woes
« Reply #32 on: April 17, 2003, 07:47:25 AM »
> ........so, in this case, any manually-set addresses must be 192.168.40.[1-64].
> Of course, if he just has the client machines obtain the IP
> adress automatically via DHCP, they'll get an address in the
> correct range, along with all the other information they need
> to operate correctly.

Thanks Dan for that clarification I'm still learning so I'm quite open to correction. After making my post I thought the same that rhys may be manually setting the NIC IP's, but in my observation he is making life hard for himself by not allowing automatic allocation via DHCP. rhys is obviously bordering on not knowing what he is doing so I thought the automatic way was the right way for him to go.

Regards
Ray

rhys

Re: Ethernet woes
« Reply #33 on: April 17, 2003, 05:10:18 PM »
Aphrodite

Microsoft(R) Windows NT(TM)
(C) Copyright 1985-1996 Microsoft Corp.

C:\>ping aphrodite

Pinging aphrodite.Sageworld [192.168.40.11] with 32 bytes of data:

Reply from 192.168.40.11: bytes=32 time<10ms TTL=128
Reply from 192.168.40.11: bytes=32 time<10ms TTL=128
Reply from 192.168.40.11: bytes=32 time<10ms TTL=128
Reply from 192.168.40.11: bytes=32 time<10ms TTL=128

C:\>ping zeus
Bad IP address zeus.
C:\>netstat -e
Interface Statistics

                           Received            Sent

Bytes                         16707           19087
Unicast packets                  12              12
Non-unicast packets             170             170
Discards                          0               0
Errors                            0               0
Unknown protocols                 0

C:\>netstat -s

IP Statistics

  Packets Received                   = 142
  Received Header Errors             = 0
  Received Address Errors            = 0
  Datagrams Forwarded                = 0
  Unknown Protocols Received         = 0
  Received Packets Discarded         = 0
  Received Packets Delivered         = 142
  Output Requests                    = 196
  Routing Discards                   = 0
  Discarded Output Packets           = 0
  Output Packet No Route             = 0
  Reassembly Required                = 0
  Reassembly Successful              = 0
  Reassembly Failures                = 0
  Datagrams Successfully Fragmented  = 0
  Datagrams Failing Fragmentation    = 0
  Fragments Created                  = 0

ICMP Statistics

                            Received    Sent
  Messages                  8           11
  Errors                    0           0
  Destination Unreachable   0           0
  Time Exceeded             0           0
  Parameter Problems        0           0
  Source Quenchs            0           0
  Redirects                 0           0
  Echos                     4           7
  Echo Replies              4           4
  Timestamps                0           0
  Timestamp Replies         0           0
  Address Masks             0           0
  Address Mask Replies      0           0

TCP Statistics

  Active Opens                        = 1
  Passive Opens                       = 1
  Failed Connection Attempts          = 0
  Reset Connections                   = 0
  Current Connections                 = 2
  Segments Received                   = 3
  Segments Sent                       = 3
  Segments Retransmitted              = 0

UDP Statistics

  Datagrams Received    = 131
  No Ports              = 4
  Receive Errors        = 0
  Datagrams Sent        = 182


C:\>netstat -n

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:1025         127.0.0.1:1026         ESTABLISHED
  TCP    127.0.0.1:1026         127.0.0.1:1025         ESTABLISHED

C:\>ipconfig

Windows NT IP Configuration

Ethernet adapter ND51001:

        IP Address. . . . . . . . . : 192.168.40.11
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . : 192.168.40.10

C:\>ipconfig -all

Windows NT IP Configuration

        Host Name . . . . . . . . . : aphrodite.Sageworld
        DNS Servers . . . . . . . . : 192.168.40.10
        Node Type . . . . . . . . . : Hybrid
        NetBIOS Scope ID. . . . . . :
        IP Routing Enabled. . . . . : No
        WINS Proxy Enabled. . . . . : No
        NetBIOS Resolution Uses DNS : Yes

Ethernet adapter ND51001:

        Description . . . . . . . . : Novell 2000 Adapter.
        Physical Address. . . . . . : 00-80-C6-04-BF-D7
        DHCP Enabled. . . . . . . . : No
        IP Address. . . . . . . . . : 192.168.40.11
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . : 192.168.40.10
        Primary WINS Server . . . . : 192.168.40.10

C:\>


Persius


C:\AWKWARD>netstat -all

Displays protocol statistics and current TCP/IP network connections.

NETSTAT [-a] [-e] [-n] [-s] [-p proto] [-r] [interval]

  -a            Displays all connections and listening ports.
  -e            Displays Ethernet statistics. This may be combined with the -s
                option.
  -n            Displays addresses and port numbers in numerical form.
  -p proto      Shows connections for the protocol specified by proto; proto
                may be TCP or UDP.  If used with the -s option to display
                per-protocol statistics, proto may be TCP, UDP, or IP.
  -r            Displays the routing table.
  -s            Displays per-protocol statistics.  By default, statistics are
                shown for TCP, UDP and IP; the -p option may be used to specify
                a subset of the default.
  interval      Redisplays selected statistics, pausing interval seconds
                between each display.  Press CTRL+C to stop redisplaying
                statistics.  If omitted, netstat will print the current
                configuration information once.


C:\AWKWARD>netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    persius:68             PERSIUS:0              LISTENING
  TCP    persius:1025           PERSIUS:0              LISTENING
  TCP    persius:137            PERSIUS:0              LISTENING
  TCP    persius:138            PERSIUS:0              LISTENING
  TCP    persius:nbsession      PERSIUS:0              LISTENING
  UDP    persius:nbname         *:*
  UDP    persius:nbdatagram     *:*

C:\AWKWARD>netstat -e
Interface Statistics

                           Received            Sent

Bytes                          5932            7016
Unicast packets                   0               0
Non-unicast packets              43              48
Discards                          0               0
Errors                            0               0
Unknown protocols                 0

C:\AWKWARD>


IPconfig before winipconfig release and renew, while zeus connected

C:\AWKWARD>ipconfig -all

Windows 98 IP Configuration

        Host Name . . . . . . . . . : PERSIUS
        DNS Servers . . . . . . . . :
        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. . . . . . . . . : 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 . . . . . . . :

1 Ethernet adapter :

        Description . . . . . . . . : 3Com EtherLink PCI
        Physical Address. . . . . . : 00-50-04-36-AB-00
        DHCP Enabled. . . . . . . . : Yes
        IP Address. . . . . . . . . : 169.254.165.173
        Subnet Mask . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . :
        DHCP Server . . . . . . . . : 255.255.255.255
        Primary WINS Server . . . . :
        Secondary WINS Server . . . :
        Lease Obtained. . . . . . . : 04 17 03 12:48:02
        Lease Expires . . . . . . . :

C:\AWKWARD>

new settings:
C:\AWKWARD>ipconfig -all

Windows 98 IP Configuration

        Host Name . . . . . . . . . : PERSIUS
        DNS Servers . . . . . . . . :
        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. . . . . . . . . : 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 . . . . . . . :

1 Ethernet adapter :

        Description . . . . . . . . : 3Com EtherLink PCI
        Physical Address. . . . . . : 00-50-04-36-AB-00
        DHCP Enabled. . . . . . . . : Yes
        IP Address. . . . . . . . . : 169.254.165.173
        Subnet Mask . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . :
        DHCP Server . . . . . . . . : 255.255.255.255
        Primary WINS Server . . . . :
        Secondary WINS Server . . . :
        Lease Obtained. . . . . . . : 04 17 03 12:48:02
        Lease Expires . . . . . . . :

C:\AWKWARD>

C:\AWKWARD>ping zeus
Unknown host zeus.

C:\AWKWARD>

C:\AWKWARD>ping 192.168.40.10

Pinging 192.168.40.10 with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

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

C:\AWKWARD>



No change there!

I've even done as suggested with SME and it hasn't made the slightest bit of difference. The only other change I've made is to renumber SME to .40.10, Aphrodite to .40.11 and Persious should be .40.12 except the auto stuff obviously didn't work.

Rhys

del

Re: Ethernet woes
« Reply #34 on: April 17, 2003, 06:37:20 PM »
Hi Rhys,
Can you log onto your sme server as root and run the command "ifconfig" without the " and yes it is F not P as you've been using in windows. Then put the results on this thread.
Cheers,
Del

Rhys

Re: Ethernet woes
« Reply #35 on: April 17, 2003, 07:06:34 PM »
Sure. How do I capture the output in order to paste it (via a floppy) to here? I don't (shudder) have to go back to such neanderthal methods as pen and paper (or tablet and chisel even) do I?

Rhys

tityityit

tiyyti
« Reply #36 on: April 17, 2003, 07:21:17 PM »
ittitiy

Per Smith

Re: Ethernet woes
« Reply #37 on: April 17, 2003, 09:42:51 PM »
Hi rhys

If you're using Putty to access zeus, all you have to do, is to mark the text. You can then paste it into any of your Windows applications.

Best regards
Per Smith

rhys

Re: Ethernet woes
« Reply #38 on: April 17, 2003, 10:03:19 PM »
Hi Per,

I can't access Zeus with putty - at all.

Rhys

Terry Brummell

Re: Ethernet woes
« Reply #39 on: April 17, 2003, 10:05:31 PM »
He doesn't have networking working yet, so putty is out of the question. So, unless you wanna learn about mounting drives I'd just write all the info down and respond to us rhys, it'll be much quicker that way, you already have enough to learn.

Terry

rhys

Re: Ethernet woes
« Reply #40 on: April 17, 2003, 10:40:49 PM »
Ah well, back to the Stone Age....

Carved into tablets of stone, pinched from the Ark of the Covenant...

ifconfig
lo link encap local loopback
inet address 127.0.0.1 mask 255.0.0.0
up loopback running mtu16436 metric 1
rx packets 0 errors 0 dropped 0 overuns 0 frame 0
tx packets 0 errors 0 dropped 0 overruns 0 carrier 0
collisions 0
rx bytes 0 (0,0,b) tx bytes 0 (0,0,b)

No difference whether Aphrodite was plugged in or not.
I noticed the red light flickered on the Aphrodite PCMCIA card and the green rermained constant. I assume the lights were the same on Zeus but I didn't look. I know zeus has lights on the ethernet card that come on and flicker.

Rhys

(wondering if he should upgrade to the abacus)

Terry Brummell

Re: Ethernet woes
« Reply #41 on: April 17, 2003, 10:52:04 PM »
That's it?  Well, here's your answer, SME doesn't see your network card...
You should have something there that says "eth0" or "eth1" with the IP info.  "lo" is the loopback interface on the SME, same as pinging "localhost" on your Windows boxes.  Is the network card in the SME of a supported variety?

rhys

Re: Ethernet woes
« Reply #42 on: April 17, 2003, 11:23:43 PM »
That's ludicrous! It's a card that's supported. It says so on the box.

Now that the menu-driven window has vanished, how can I get it back? With that at least I can cycle through the drivers to try to get SME to recognise a card that is supported by Linux. Maybe the card manufacturers were relying on a more up-to-date version of Red Hat than went into Linux.

Rhys

del

Re: Ethernet woes
« Reply #43 on: April 17, 2003, 11:36:26 PM »
Hi Rhys,
Maybe it is a faulty nic? If you are based in the UK go out and buy a Genius NIC they worked every time for me when I was living in the UK, I only wish I could buy them here in the US.
Del

rhys

Re: Ethernet woes
« Reply #44 on: April 18, 2003, 12:51:29 AM »
No. Looks like SME is faulty. It seems to want to call my NIC, Tulip this time. This time though, I'm getting eth 0 and lots more info. I still can't find it in Network Neighbourhood.

All I can say is thank God somebody's giving me a copy of NT4 server.

Rhys