Topic: Ethernet woes

[Per Smith]

Hi Rhys

One thing I don't quite understand:
You say in an earlier post, that you've changed the IP address from ..40.1 to ..40.10.
That indicates, that your NIC is installed in Zeus. Is that something you've installed manually, or was it detected automatically?
If it was manually added, try to remove it, and try to automatically detect it again.

Do you use your hub now, or are you still using the crossover cable?
If you use the crossover cable, you may need to reboot Zeus when connecting, in order to bring up the interface.

Best regards
Per Smith

[Per Smith]

Hi Rhys,

Forget Network Neighbourhood. That will probably first show up when you've enabled it in server-manager.

Can you ping it after you've gotten the new info?

-Per

[del]

Post new info here

[Thomas Kristensen]

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



Publicly admitting software piracy is generally not a smart thing to do. But hey what the hell, you don't seem like a person who does anything smart...

I have personally deployed more than a dozen SME servers in organisations ranging from 2 to 73 users. I've deployed it as a standalone server and as a server working alongside Windows servers and other Unix servers, in environments where clients were Windows, Macs and Linux.

I've met my share of problems along the way and you know what: they've all been solvable if you know what you're doing. I've been following your ramblings over the past couple of weeks and one thing is pretty clear: you completely lack the fundamental skills for configuring, not to mention troubleshooting, a network. You need to do a whole lot of RTFM and STFW before you start blaiming your own lack of skills on SME.

SME works. Period. No buts, no ifs. Read the HCL, check your hardware against the HCL, read and do what it says in the manual and you'll have a server running in less than one hour from the time you start your install. That's more than what can be said for ths OS you apparently see as your savior, NT. You would be lucky to get that thing running and set up to perform the same things as a SME server within a day. I'm not bashing on Microsoft, I've done my share of server installs and configurations on that platform as well...

BTW: NT4 is EOL, you might want to go for a copy of W2K server. And your expertise in configuring SME certainly suggests that you would have absolutely no problems in configuring Active Directory, DNS and such, not to mention setting up a mailserver like Exchange 2000. Yeah right, and pigs fly...



/TK

[rhys]

Software Piracy??? The guy's upgraded to W2K. It's a freebie (original disks & manual etc). I'm one of those people who (maybe misguidedly rings Microsoft every time I see pirated MS software on sale).

I matched the addresses on Aphrodite and those on Zeus. Zeus is currently configured as server only.

I pinged Zeus from Aphrodite and had the following:

C:\>ping zeus

Pinging zeus.Sageworld [192.168.40.10] with 32 bytes of data:

Reply from 192.168.40.10: bytes=32 time<10ms TTL=64
Reply from 192.168.40.10: bytes=32 time<10ms TTL=64
Reply from 192.168.40.10: bytes=32 time<10ms TTL=64
Reply from 192.168.40.10: bytes=32 time<10ms TTL=64

C:\>
C:\>

BUT... Why can't I see Zeus in Network Neighbourhood and why can't I ping Aphrodite from Zeus?

I managed to get the server-manager window up on Aphrodite too (using IE 3.5).

I guess this means I'm getting there albeit slowly. This is what the server-manager window announced. I've already pasted (earlier) the ipconfig for Aphrodite (running NT4).

Review configuration
Networking Parameters
Server Mode serveronly
Local IP address / subnet mask 192.168.40.10/255.255.255.0
Gateway 192.168.40.10
Additional local networks No additional networks defined
DHCP server enabled
Beginning of DHCP address range 192.168.40.65
End of DHCP address range 192.168.40.250
Server names
DNS server 192.168.40.10
Web server www.sageworld
Proxy server proxy.sageworld:3128
FTP server ftp.sageworld
SMTP, POP, and IMAP mail servers mail.sageworld
Domain information
Primary domain sageworld
Virtual domains No virtual domains defined
Primary web site http://www.sageworld
Mitel Networks SME Server manager http://zeus/server-manager/
Mitel Networks SME Server user password panel http://zeus/user-password/
Email Addresses useraccount@sageworld
firstname.lastname@sageworld
firstname_lastname@sageworld
 
Now, what's the next step (apart from connecting Persius, Aphrodite and Zeus via my hub)?

Rhys

[Terry Brummell]

By George I think he got it!  Good for you!  OK, moving along, (IE 3.5??  what's with that?)  If you can ping Zeus from Aphwhatever, the other should be possible too.  Try using the IP address's instead of the names.  There may be something to sort out in WINS before naming works.
Some things to keep in mind:
1.  All 3 machines should have unique IP adresses withing the 192.168.40.1-64 range so it doesn't interfere with the DHCP addresses
2.  All machines should have the same subnet mask (255.255.255.0 in this case)
3.  All machines should have the same workgroup name.  In the SME that is assigned in the server-manager in the Workgroup menu, do not bother making the SME the domain controller at this time.  Set the workgroup on your Windows machines somewhere in the Control Panel (I forget exactly where now).

Make those changes and report back what happens.

Terry

[rhys]

As an aside. Can anybody recommend a good book (not a great tome) to explain simply how servers, I/Ps, subnets, masks and the various protocols work?

I'm thinking of something like the Hodder and Stoughten series (doubt they've got a book to cover it), not great big doorsteps like Sams etc produce.

I've only just changed from BNC to RJ45 so I'm combining a new machine built with ATX plus a new cabling system plus a new O/S. Until now I've been happily running AT systems with BNC cabling and Windows 95/98/NT4 and NT4's only a recent development for me. So, I'm still a mite confused by all these new things.

Rhys

[Ray Mitchell]

Rhys

> Pinging zeus.Sageworld [192.168.40.10] with 32 bytes of data:
> Reply from 192.168.40.10: bytes=32 time<10ms TTL=64

Yes looks like you have got it !!
HOORAY, SCREAMS, WHOOPS and YELLS of delight !!!

> Now that the menu-driven window has vanished, how can I get
> it back?

It did not vanish, you told sme to require log in to display the Server console screen (rather than auto display). Log in as admin to get the server console, log in as root to get the command prompt. (the admin password is the same for both).

> Now, what's the next step (apart from connecting Persius, Aphrodite and Zeus
> via my hub)?

I think that IS the next step.
Just make sure that all your PC's and server are in the same workgroup, set this in sme server manager/workgroup panel, and in Windows in Control panel/Network..

> Software Piracy??? The guy's upgraded to W2K. It's a freebie

If it is truly an upgrade (ie costs less than a full purchase), then the software license transfers to the new version (W2K) but remains explicitly attached to the old version, meaning that technically the old NT4 cannot be used by anyone, including the original license holder, as he is the one license to run the new W2K version which he is now using.
Your answer only applies if the new purchase was for a FULL version of the W2K program (not an upgrade), which effectively means a new separate licence was purchased.

Happy using of sme (finally)

Regards
Ray Mitchell

[rhys]

This is interesting. I can communicate with Zeus from Aphrodite (NT4) but not from Persius (Win 98). I can ping Zeus from Persius but can't get http://zeus/server-manager/ to come up. Also, I can't see Persius in Persius' Network Neighbourhood, now Zeus. I've done an ipconfig and a c&p of the pings. Zeus is supposed to be 192.168.40.10 (that's how I assigned it, anyway) so I'm puzzled now as to why it's pinging as 192.168.40.12 (which was the number assigned to Persius). Any ideas on any of these questions - anybody?

C:\AWKWARD>ipconfig -all

Windows 98 IP Configuration

        Host Name . . . . . . . . . : zeus.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

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. . . . . . . . : No
        IP Address. . . . . . . . . : 192.168.40.12
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . : 192.168.40.10
        Primary WINS Server . . . . : 192.168.40.10
        Secondary WINS Server . . . :
        Lease Obtained. . . . . . . :
        Lease Expires . . . . . . . :

C:\AWKWARD>
C:\AWKWARD>ping zeus

Pinging zeus.sageworld [192.168.40.12] with 32 bytes of data:

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

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


Rhys

[Dan Brown]

Well, why "Persius" is pinging 192.168.40.12 is obvious--it thinks it's zeus.  That's also why you can't get to the server manager page.

[Rhys]

Why does Persius think it's Zeus? It's called Persius on the Identification tab of Network Neighbourhood.

I'll have a little play with the settings to try to work on this one unless somebody can tell me exactly where I'm going wrong.

Rhys

[Dan Brown]

Why persius thinks it's zeus I don't know, but here's what makes me say that (from your post):

C:\AWKWARD>ipconfig -all

Windows 98 IP Configuration

Host Name . . . . . . . . . : zeus.sageworld


    Try taking a look at the DNS configuration.  The name and domain it asks for there are for the machine you're configuring, not for your DNS server.

[Rhys]

I think this is better. I can't find out how to fix the fact that I can't now ping by name.

C:\AWKWARD>ipconfig -all

Windows 98 IP Configuration

        Host Name . . . . . . . . . : Persius
        DNS Servers . . . . . . . . : 192.168.40.12
        Node Type . . . . . . . . . : Broadcast
        NetBIOS Scope ID. . . . . . :
        IP Routing Enabled. . . . . : No
        WINS Proxy Enabled. . . . . : No
        NetBIOS Resolution Uses DNS : Yes

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. . . . . . . . : No
        IP Address. . . . . . . . . : 192.168.40.12
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . : 192.168.40.10
        Primary WINS Server . . . . :
        Secondary WINS Server . . . :
        Lease Obtained. . . . . . . :
        Lease Expires . . . . . . . :

C:\AWKWARD>

When I ping, I get:
C:\AWKWARD>ping 192.168.40.12

Pinging 192.168.40.12 with 32 bytes of data:

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

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

C:\AWKWARD>ping persius

Pinging Persius [192.168.40.12] with 32 bytes of data:

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

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

C:\AWKWARD>ping zeus
Unknown host zeus.

C:\AWKWARD>

[Dan Brown]

No, it needs the IP address(es) of your DNS server(s), but the name and domain you enter are for the client machine.

[Rhys]

Hmm. Interesting. I fixed it all - and made sure that the setup in Persius was the same as in Aphrodite. The only differences between Persius and Aphrodite are:

Persius runs a firewall, an antivirus and a dial-up modem. Other than that, they are pretty similar (aside from the fact Persius runs Win98 and Aphrodite runs NT4).

I can see Aphrodite in Aphrodite's Network Neighbourhood. I can't see Persius in Persiuses Network neighbourhood. Zeus doesn't appear anywhere.

I can ping Zeus from either by name or number now.

But...while everything's perfect on Aphrodite, Persius is now having major problems:

1. Norton Antivirus keeps crashing about every other boot.
2. Zone Alarm keeps crashing about every other boot.

Those two must share a .dll, I'd guess.

When I want to access the Internet for web pages, I can do it via  Netscape but Internet Explorer (my favoured browser) comes up with the following:

The requested URL could not be retrieved

--------------------------------------------------------------------------------

While trying to retrieve the URL: http://www.dcresource.com/cgi-bin/WebX.dcrp

The following error was encountered:

Unable to determine IP address from host name for www.dcresource.com
The dnsserver returned:

Server Failure: The name server was unable to process this query.
This means that:

 The cache was not able to resolve the hostname presented in the URL.
 Check if the address is correct.
Your cache administrator is admin@sageworld.



--------------------------------------------------------------------------------
Generated Sat, 19 Apr 2003 00:24:19 GMT by zeus.sageworld (Squid/2.4.STABLE6)

Very interesting. Has anybody any ideas about that.

While we're on the subject - I'd guess you're all going to say buy a pci modem: how do I know when the modem on the server has hung up and when it's dialled or is in use?

Rhys