Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: dexter on October 14, 2004, 01:16:15 PM

Title: Problems accessiing Inet...
Post by: dexter on October 14, 2004, 01:16:15 PM
My SME works in Server and Gateway mode... I can still "ping" every outside address, SSH to and from server, FTP and Mail server works fine, but NO WEB access from local network. Can somebody give me some directions please ?!!.

Andrej
Title: Problems accessiing Inet...
Post by: meanpenguin on October 14, 2004, 11:17:51 PM
post the output of ipconfig /all from the workstation.

Ed
Title: Problems accessiing Inet...
Post by: cc_skavenger on October 14, 2004, 11:57:28 PM
can you ping the server from the workstation?  If not, it could be a hardware issue (network cards, cables, switch/hub).  is there a switch/hub in place or is the workstation connected directly to the server (if connected directly, is a crossover cable being used?).  are you using dhcp or assigned IPs?  tell us more about your setup.
Title: Problems accessiing Inet...
Post by: dexter on October 15, 2004, 08:17:06 AM
Tx, for replies, folks.

Of course I can PING my server as all IPs on the I-net. All networks works (ping, ports 22, 21, 110, 25) including Web server which can be reached from LAN and WAN side. Only my clients CAN NOT reach the WEB using browser...
Title: Problems accessiing Inet...
Post by: meanpenguin on October 15, 2004, 11:45:49 PM
Since you don't want to help out and display your ipconfig info, try this and post what results you get.
Can you ping it?

ping 216.109.112.135   (it's yahoo.com)

Ed
Title: Problems accessiing Inet...
Post by: bobk on October 16, 2004, 12:57:43 AM
Quote from: "dexter"
Tx, for replies, folks.

Of course I can PING my server as all IPs on the I-net. All networks works (ping, ports 22, 21, 110, 25) including Web server which can be reached from LAN and WAN side. Only my clients CAN NOT reach the WEB using browser...


Can you also ping a URL from workstations on the network? For example: if you can ping 216.109.112.135 but can not ping yahoo.com then you most likely have a DNS issue.
Title: Problems accessiing Inet...
Post by: smeghead on October 16, 2004, 09:29:55 AM
Assuming DNS is working and you still can't access the web then ...

This issue can be caused by squid failing to start or being locked up - James Price put together a nice Squid cache app that when used in SME6 does not initialise the cache directive properly (on install) in the squid.conf file; squid then fails.

Run: service squid status

It will tell you if squid is running and/or its condition.
Title: Problems accessiing Inet...
Post by: dexter on October 16, 2004, 12:34:32 PM
Thanks again:

All your sugestions are quite good, but I was already trid them all. If I make some recap...

PING: OK from inside and outside
DNS: also OK (if I ping some outside address, yahoo or sommething else. I preffer my ISP )
MAIL: OK (spamassasin, clamav, qmail )
WEB: OK (also available from outside www.prva-gimnazija.org - try yourself )

Nice try smeghead, I am going to try this hint ...

Squid: Status OK, but for every Case I am going to restart the service. Till monday I can not test client from LAn, so all replies will be delayed till monday.


Here it is:

eth0      Link encap:Ethernet  HWaddr 00:60:97:B5:0E:2C
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          EtherTalk Phase 2 addr:65280/227
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:350 errors:0 dropped:0 overruns:0 carrier:350
          collisions:0
          RX bytes:0 (0.0 b)  TX bytes:74325 (72.5 Kb)

eth1      Link encap:Ethernet  HWaddr 00:A0:D2:A4:47:78
          inet addr:193.2.129.160  Bcast:193.2.129.191  Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:112180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:139541 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:19375445 (18.4 Mb)  TX bytes:113658643 (108.3 Mb)

eth2      Link encap:Ethernet  HWaddr 00:50:BF:D6:F4:1F
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:0 (0.0 b)  TX bytes:72723 (71.0 Kb)

ipsec0    Link encap:Ethernet  HWaddr 00:A0:D2:A4:47:78
          inet addr:193.2.129.160  Mask:255.255.255.192
          UP RUNNING NOARP  MTU:16260  Metric:1
          RX packets:0 errors:0 dropped:0 overruns: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)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          EtherTalk Phase 2 addr:0/0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6758 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6758 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:788835 (770.3 Kb)  TX bytes:788835 (770.3 Kb)
Title: Problems accessiing Inet...
Post by: meanpenguin on October 17, 2004, 10:36:05 AM
I think I know what the problem is....
Hopefully this will be my last attempt so it better be correct.. Right?

Turn off the "Auto Detect Settings" in IE (Tools->Internet Options->Connections->LAN Settings
You are using IE right?

Ed
Title: Problems accessiing Inet...
Post by: dexter on October 17, 2004, 12:20:30 PM
Tx, Ed!

Yes I am using IE on some clients, but I personaly use Firefox, without automatic settings for proxy adjustment. Tx, for help anyway.