Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Bob Stirling on June 12, 2002, 06:38:13 AM
-
Hi to All,
I recently installed Mitel Networks SME Server V5.1.2
as a private server/gateway for my office network, mainly so I could re-boot my Windows machines without dropping my Dial-up connection.
I now find that I am having trouble with all types of FTP and ping programs,
the FTP programs are very slow and unreliable and any ping I try to initiate gives a no response error.
I know absolutely nothing about Unix/Linux but would really like to try and resolve these problems as they are making my working life a real hassle!
Any suggestions will be gratefully received.
Thanks,
Bob
-
Bob,
I think the problem lies with your Windows machine itself. When installing E-Smith I assume you configured it as a router/gateway. That being said, please ensure your Windows machine has the following network configuration:
IP Address [Assigned by DHCP]
Default Gateway [ IP Address of E-Smith Box]
DNS Servers [ IP Address of E-Smith Box]
Also ensure you're Windows machine doesn't have any third party routing software, such as Wingate, etc.
Your E-Smith machine in your case should be as transparent as an enterprise Cisco router.
Hope this helped,
Nathan
-
Hi Nathan,
Wow!! FTP and HTTP are now working absolutely perfectly Ü!
I still have a problem with ping and trace though :{
Thank you very much for the help,
Bob
-
Bob, if you would type at the Run prompt on your Windows machine:
ipconfig -all > c:\ipconfig.txt
And paste me the contents of c:\ipconfig.txt I could probably tell you why tracert doesn't work.
Glad everything is working correctly so far,
Nathan
-
i also have the same problem
my e-smith box can't be pinged from internal/external network.
it always blocks the ping there. the box itself can do both ping and tracert
cheers
Aladdin
-
Hi Nathan,
I really appreciate you helping this way, I don't know much about networks per se, I have never really needed to!
Windows IP Configuration
Host Name . . . . . . . . . : sawdust.splothome.com.au
DNS Servers . . . . . . . . : 192.168.0.1
Node Type . . . . . . . . . : Hybrid
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : Yes
0 Ethernet adapter :
Description . . . . . . . . : 3Com 3C90x Ethernet Adapter
Physical Address. . . . . . : 00-10-4B-2F-69-B5
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . : 192.168.0.1
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 06 12 02 11:02:52 PM
Lease Expires . . . . . . . : 06 13 02 11:02:52 PM
1 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 . . . . . . . :
-
Everything looks good. Do you have any firewalling software on your Windows machine such as BlackICE, Conseal, McAfee, Norton, etc? If so, remove it, it isn't necessary. Other than that your local Network configuration looks correct.
Hope this helped,
Nathan
-
Hi Nathan,
My firewall was disabled but I removed it anyway, still no luck.
This problem has really only been happening since I changed the server over from gateway/server to private gateway/server, prior to that I could ping and trace.
I can manage without, it's just at times I need to confirm DNS's for sites that I am delegating, just so I can tell when to activate them and any mail addresses they may have.
Thanks again for all your help,
Bob
-
Aladdin, from my understanding, its normal when you set up the e-smith as a private gateway for it to not respond to pings, or allow pings thru.
Not responding to pings is actually a good thing - if you've ever had a ping attack, you'd know.
If you want it to respond to pings or allow pings to pass thru, change it to a public gateway...