Topic: Okay, this is getting stupid...

[Bruce]

Why is it that everyone is missing the boat here.

Dave, I think your problem is really related to the fact that your SME server stops providing services on a sporatic basis.  My server is not as heavily used, and I have only one server, directly hooked to the DSL Modem.  About every two weeks, services die.  I have to reboot the server, and everything is fine.

I'm running an AMD K6-2 650 with 256MB and an 80 GB drive.

I'm beginning to thing it has something to do with network traffic overloading "something," but I havn't been able to identify what.  Mine always seems to happen in the morning hours.

Change the time lines, and it sounds like you and I are experiencing the same problem.  I've subscribed to forwarding my logs to Mitel, but haven't seen any results.  I wish you better luck.

[Bill Talcott]

We're using SME 5.0b3 here, and have a similar problem. Occasionally, the local NIC just seems to stop working. I can dial in from a LAN PC to another ISP, and ping the external IP of the SME, but I cannot ping the internal IP. Like Dave, there seems to be no pattern, it just happens sometimes, and a reboot fixes it.

Dave, if you just want to run a few simple services on your XP box, you may be able to use port forwarding through the SME, as others have suggested. http://myezserver.com/docs/mitel/ipportfw-howto.html is great. Just pick the port and protocol, and a LAN destination to forward them to. But as was stated already, that really has nothing to do with your problem, just something else to think about.

We haven't had any problems with ours lately, and it only happened maybe once every few weeks before, so it wasn't much of a problem then. But if there is a valid reason for this, then finding a fix would be nice...

[Dave Wilson]

Well, I've tried the whole plug modem into server, plug server into hub, plug all other computers into hub thing and it's been working for over 12 hours now.  We'll if it keeps going.  I'll update here over the next few days to keep you all informed.

[Dave Wilson]

Okay, it looks like my problem with dropping out of existence is finally gone.  However, the problem with it taking time to connect for e-mail and FTP is still there.  Any thoughts?

[Don Bahler]

I have seen problems somthing like this in a straight cable modem to nic connection. Cox cable (Toshiba pcx2000 cable modem to 3com 905tx nic to soyo motherboard in a AMD 550. We ended up putting a Linksys 100 card in the machine and all is well.  I have also had nearly the same expericence with a Realtek NIC in an AMD 1g. you may need to check the MB manufacturer & or NIC manufacturer  to see if you need to update drivers.  It can be a real pain to find the info you need but if you have a VIA chipset on the motherboard and a 3com NIC I think you may need to update the mb drivers.

That's my 2 cents

[Howard Dobko]

Hi, just my 2 cents after the fact ...
I am assuming that you have two different static IPs for the XP and the e-smith box from your ISP.  I am assuming that your hub is connected directly to your modem via the uplink port.  You also have DHCP enabled on the single NIC in the e-smith box.  Could there not be a problem with having both the static external IP and the non-routeable internal IP on the same NIC ... and DHCP as well?  Buy another hub and another NIC ...

Modem -> uplink HUB 1
XP box -> HUB 1 with static ISP address
e-smith -> NIC 1 -> HUB 1 with static ISP address (ext interface)
e-smith -> NIC 2 -> HUB 2 with internal non-routeable IP (int interface)

Now connect all your local LAN boxes with DHCP on HUB 2 and connect any other static ISP address boxes in the DMZ on HUB 1.

Later, Howard

[Tom]

I think I have a simular problem.  I'm trying to put an E-Smith 5.0 in between the DSL modem and hub on a Cox service.  Connecting direct, the E-Smith cannot find the internet.  From Howard's diagram it looks like i need either an extra uplink hub inbetween the modem and the server or to make the connection with a crossover cable.  Does that sound right?

[John Goodwin]

Hi Tom,

I doubt adding a hub to the mix will fix your problem.  I use cox roadrunner also and I can give you a few suggestions from my experience, though your setup may differ based on your location.  My E-smith box is directly connected to my cable modem and it works great.  Here are some suggestions on what could be the cause:

1.  You didn't reset your modem.  When I changed over to the e-smith box from a different pc, I had to unplug the power from the modem for a few minutes.

2.  Ethernet drivers - I used linksys nics and had many problems that I eventually was able to correct by updating drivers.

3.  You have the internal and external connections reversed.  I did this once by accident, just switch the connections and you will be good.

Like I said, these suggestions are based on my experience with cox.

Hope this helps,
John

[Tom]

What did you put in for the dhcp?  account name or machine address?John Goodwin wrote:
>
> Hi Tom,
>
> I doubt adding a hub to the mix will fix your problem.  I use
> cox roadrunner also and I can give you a few suggestions from
> my experience, though your setup may differ based on your
> location.  My E-smith box is directly connected to my cable
> modem and it works great.  Here are some suggestions on what
> could be the cause:
>
> 1.  You didn't reset your modem.  When I changed over to the
> e-smith box from a different pc, I had to unplug the power
> from the modem for a few minutes.
>
> 2.  Ethernet drivers - I used linksys nics and had many
> problems that I eventually was able to correct by updating
> drivers.
>
> 3.  You have the internal and external connections reversed.
> I did this once by accident, just switch the connections and
> you will be good.
>
> Like I said, these suggestions are based on my experience
> with cox.
>
> Hope this helps,
> John

[John Goodwin]

I used machine address.

[John Goodwin]

HI Tom,

I didn't have to do anything directly with Cox, but of course it could be different in a different location.  I have another sme box in another area that is on ATT broadband and you have to register the mac id of your ethernet card with them in order to get a new nic to work.  I will tell you that cox at my location blocks port 80 so you won't be able to get external access unless you configure apache to listen to a different port and use a dns service to forward request to the new port.  You can get access externally in my location using 8080 (SSL).

Hope this helps,
John