11:25 a.m.
I have reviewed Adam Gautier's recent post on mounting a Windows shared
document folder on his Linux box with interest. I have tried to do the
a similar thing for our system but am unable to succeed.
I have xyz set up as a WindowsXP Professional machine, and I am able to
access the
Shared Documents folder on xyz from other Windows machines but have not
been able to mount it with FC1. I have xyz listed in my hosts file, and
have ALL: xyz : allow in my hosts.allow file. I have also turned off
iptables to make sure there was no conflict.
My fstab entry is:
xyz:/ /mnt/ceb smbfs noauto,user,user=guest 0 0
When I use the command:
mount xys:/
I receive :
This command is designed to be run from within /bin/mount by giving
the option '-t smbfs'. For example:
mount -t smbfs -o username=tridge,password=foobar //fjall/test
/data/test
I have tried to use the syntax in the error message but get the same
results.
Any help would be appreciated.
Thank you,
Greg Ennis
12:14 p.m.
On Wed, 2004-04-28 at 09:25, Greg Ennis wrote:
I have reviewed Adam Gautier's recent post on mounting a Windows
shared
document folder on his Linux box with interest. I have tried to do the
a similar thing for our system but am unable to succeed.
I have xyz set up as a WindowsXP Professional machine, and I am able to
access the
Shared Documents folder on xyz from other Windows machines but have not
been able to mount it with FC1. I have xyz listed in my hosts file, and
have ALL: xyz : allow in my hosts.allow file. I have also turned off
iptables to make sure there was no conflict.
My fstab entry is:
xyz:/ /mnt/ceb smbfs noauto,user,user=guest 0 0
When I use the command:
mount xys:/
I receive :
This command is designed to be run from within /bin/mount by giving
the option '-t smbfs'. For example:
mount -t smbfs -o username=tridge,password=foobar //fjall/test
/data/test
xys:/ is not a Windows share name (or format). You need something like
//xys/share (//xys/c$ for example).
Forrest
1:10 p.m.
On Wed, 2004-04-28 at 12:14, Taylor, ForrestX wrote:
xys:/ is not a Windows share name (or format). You need something like
//xys/share (//xys/c$ for example).
Forrest
Forrest,
Thanks very much!!! I used your syntax and it worked. Now I need to
find a way to bypass the password question and I should be home free!!!
Greg
1:23 p.m.
Is there somewhere this information is listed on the
net and can it be used to share a folder on a dual
boot machine. I still don't understand how 'wine'
works would this be helpful?
Thanks,
Mac
--- Greg Ennis <PoMec(a)PoMec.Net> wrote:
On Wed, 2004-04-28 at 12:14, Taylor, ForrestX wrote:
>
>
> xys:/ is not a Windows share name (or format).
You need something like
> //xys/share (//xys/c$ for example).
>
> Forrest
>
>
Forrest,
Thanks very much!!! I used your syntax and it
worked. Now I need to
find a way to bypass the password question and I
should be home free!!!
Greg
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
1:48 p.m.
New subject: Mounting partition on dual-boot machine [was: Re: Mounting a Windows XP Shared Folder]
On Wed, 2004-04-28 at 11:23, Mac wrote:
Is there somewhere this information is listed on the
net and can it be used to share a folder on a dual
boot machine. I still don't understand how 'wine'
works would this be helpful?
Do you mean that you want to mount your Windows partition in Linux on a
dual boot machine? Is the partition FAT32 or NTFS? Try these commands
as root:
mkdir /mnt/windows
mount /dev/hda1 /mnt/windows
Forrest
--
2:19 p.m.
New subject: Mounting partition on dual-boot machine [was: Re: Mounting a Windows XP Shared Folder]
Thank you Forrest, I'll try that command when I return
to the Linux side of my dual boot machine.
Mac
--- "Taylor, ForrestX" <forrestx.taylor(a)intel.com>
wrote:
On Wed, 2004-04-28 at 11:23, Mac wrote:
> Is there somewhere this information is listed on
the
> net and can it be used to share a folder on a dual
> boot machine. I still don't understand how 'wine'
> works would this be helpful?
Do you mean that you want to mount your Windows
partition in Linux on a
dual boot machine? Is the partition FAT32 or NTFS?
Try these commands
as root:
mkdir /mnt/windows
mount /dev/hda1 /mnt/windows
Forrest
--
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
2:32 p.m.
New subject: Mounting partition on dual-boot machine [was: Re: Mounting aWindows XP Shared Folder]
fedora-list-bounces(a)redhat.com wrote:
Thank you Forrest, I'll try that command when I return
to the Linux side of my dual boot machine.
Mac
--- "Taylor, ForrestX" <forrestx.taylor(a)intel.com>
wrote:
> On Wed, 2004-04-28 at 11:23, Mac wrote:
>> Is there somewhere this information is listed on the
>> net and can it be used to share a folder on a dual
>> boot machine. I still don't understand how 'wine'
>> works would this be helpful?
>
> Do you mean that you want to mount your Windows
> partition in Linux on a
> dual boot machine? Is the partition FAT32 or NTFS? Try these
> commands as root:
>
> mkdir /mnt/windows
> mount /dev/hda1 /mnt/windows
>
> Forrest
> --
>
You may need to alter your mount command slightly:
mount -t ntfs /dev/hda1 /mnt/windows
is what worked for me.
-Don
4:41 a.m.
New subject: Mounting partition on dual-boot machine [was: Re: Mounting aWindows XP Shared Folder]
Don Levey wrote:
fedora-list-bounces(a)redhat.com wrote:
>Thank you Forrest, I'll try that command when I return
>to the Linux side of my dual boot machine.
>
>Mac
>
>--- "Taylor, ForrestX" <forrestx.taylor(a)intel.com>
>wrote:
>
>
>>On Wed, 2004-04-28 at 11:23, Mac wrote:
>>
>>
>>>Is there somewhere this information is listed on the
>>>net and can it be used to share a folder on a dual
>>>boot machine. I still don't understand how 'wine'
>>>works would this be helpful?
>>>
>>>
>>Do you mean that you want to mount your Windows
>>partition in Linux on a
>>dual boot machine? Is the partition FAT32 or NTFS? Try these
>>commands as root:
>>
>>mkdir /mnt/windows
>>mount /dev/hda1 /mnt/windows
>>
>>Forrest
>>--
>>
>>
>>
You may need to alter your mount command slightly:
mount -t ntfs /dev/hda1 /mnt/windows
is what worked for me.
-Don
That only gives me the following:
mount: fs type ntfs not supported by kernel
5:59 a.m.
New subject: Mounting partition on dual-boot machine [was: Re: Mounting aWindows XP Shared Folder]
Am So, den 02.05.2004 schrieb John Lagrue um 11:41:
That only gives me the following:
mount: fs type ntfs not supported by kernel
Because the Fedora kernel does not support NTFS. That was already often
explained here on the list and is part of the unofficial FAQ
http://fedora.artoo.net/faq/#NTFS
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2188.nptl
Sirendipity 12:57:55 up 6 days, 11:46, load average: 1.40, 1.18, 1.11
[ Γνωθι σ'αυτον - gnothi seauton ]
my life is a planetarium - and you are the stars
3:19 p.m.
New subject: Mounting partition on dual-boot machine [was: Re: Mounting aWindows XP Shared Folder]
On Sun, 2004-05-02 at 02:41, John Lagrue wrote:
>fedora-list-bounces(a)redhat.com wrote:
>
>
>>Thank you Forrest, I'll try that command when I return
>>to the Linux side of my dual boot machine.
>>
>>Mac
>>
>>--- "Taylor, ForrestX" <forrestx.taylor(a)intel.com>
>>wrote:
>>
>>
>>>On Wed, 2004-04-28 at 11:23, Mac wrote:
>>>
>>>
>>>>Is there somewhere this information is listed on the
>>>>net and can it be used to share a folder on a dual
>>>>boot machine. I still don't understand how 'wine'
>>>>works would this be helpful?
>>>>
>>>>
>>>Do you mean that you want to mount your Windows
>>>partition in Linux on a
>>>dual boot machine? Is the partition FAT32 or NTFS? Try these
>>>commands as root:
>>>
>>>mkdir /mnt/windows
>>>mount /dev/hda1 /mnt/windows
>>>
>>>Forrest
>
That only gives me the following:
mount: fs type ntfs not supported by kernel
You need to download and install the kernel-ntfs rpm from:
http://linux-ntfs.sourceforge.net/rpm/index.html
It should be fairly straight forward, but if you run into trouble,
repost here.
Forrest
--
4:42 p.m.
New subject: Mounting partition on dual-boot machine [was: Re: Mounting aWindows XP Shared Folder]
Taylor, ForrestX wrote:
On Sun, 2004-05-02 at 02:41, John Lagrue wrote:
>>fedora-list-bounces(a)redhat.com wrote:
>>
>>
>>
>>>Thank you Forrest, I'll try that command when I return
>>>to the Linux side of my dual boot machine.
>>>
>>>Mac
>>>
>>>--- "Taylor, ForrestX" <forrestx.taylor(a)intel.com>
>>>wrote:
>>>
>>>
>>>
>>>>On Wed, 2004-04-28 at 11:23, Mac wrote:
>>>>
>>>>
>>>>
>>>>>Is there somewhere this information is listed on the
>>>>>net and can it be used to share a folder on a dual
>>>>>boot machine. I still don't understand how 'wine'
>>>>>works would this be helpful?
>>>>>
>>>>>
>>>>
>>>>Do you mean that you want to mount your Windows
>>>>partition in Linux on a
>>>>dual boot machine? Is the partition FAT32 or NTFS? Try these
>>>>commands as root:
>>>>
>>>>mkdir /mnt/windows
>>>>mount /dev/hda1 /mnt/windows
>>>>
>>>>Forrest
>>
>That only gives me the following:
> mount: fs type ntfs not supported by kernel
You need to download and install the kernel-ntfs rpm from:
http://linux-ntfs.sourceforge.net/rpm/index.html
It should be fairly straight forward, but if you run into trouble,
repost here.
Or get a pre-compiled binary from
http://www.rhil.net/kernelstuff/modules.html
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens(a)vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- If it's stupid and it works...it ain't stupid! -
----------------------------------------------------------------------
3:03 p.m.
New subject: Network troubleshooting, any experts?
Hi list,
First let me say that the particular server that I am trying to
troubleshoot is not Fedora, but
RedHat 9. As I am subscribed to this list, I thought it would be a good
place to ask.
At this particular company we have a webserver, that sits behind a
firewall/router. All incoming port 80
traffic is directed to this server. All computers in the company reside
internally on 123.123.123.* ip addresses.
All DNS resolution is done externally.
Now the problem is that all computers on the network can browse the
internet and do various chores like
telnet and ssh with no problem, except for the web server. I can ssh,
telnet etc. to other computers on the internal network
from the web server but not to the outside world.
Some oddities:
My resolv.conf file has the ip addresses of my DNS servers. If I ping
an internet address I get back the ip resolution ok, yet I cannot
telnet to either of my DNS servers on port 53 from the web server. So
how am I getting back ip addresses when I ping?
Traceroute and ping respond ok, but no other utilities respond. They
all time out. I ran some tcpdump's telneting to yahoo.com and the DNS
server and I've
included those below if it's helpful to anyone.
I have no firewall running, and just to be sure I've flushed the
iptables and ran the /etc/rc3.d/iptables script with the -stop flag.
I've also talked to the isp( it's their router ) and they claim that if
all the other computers can get web access then so should
the webserver.
If anyone has ANY suggestions it would be most helpful.
Cheers,
Elam Daly
Whiteware Inc.
TCPDUMP to YAHOO.COM telnet port 80:
15:20:05.621044 123.123.123.240.1065 > sprite.wwnet.net.domain: 29834+
AAAA? www.yahoo.com. (31) (DF)
15:20:05.700534 sprite.wwnet.net.domain > 123.123.123.240.1065: 29834
1/1/0 (137)
15:20:05.700874 123.123.123.240.1065 > sprite.wwnet.net.domain: 29835+
A? www.yahoo.com. (31) (DF)
15:20:05.723337 sprite.wwnet.net.domain > 123.123.123.240.1065: 29835
9/9/9 CNAME[|domain]
15:20:05.724132 123.123.123.240.1065 > sprite.wwnet.net.domain: 1558+
PTR? 68.118.109.216.in-addr.arpa. (45) (DF)
15:20:05.830093 sprite.wwnet.net.domain > 123.123.123.240.1065: 1558*
1/5/5 (276)
15:20:05.830519 123.123.123.240.1065 > sprite.wwnet.net.domain: 1559+
PTR? 65.118.109.216.in-addr.arpa. (45) (DF)
15:20:05.893671 sprite.wwnet.net.domain > 123.123.123.240.1065: 1559*
1/5/5 (276)
15:20:05.894048 123.123.123.240.1065 > sprite.wwnet.net.domain: 1560+
PTR? 108.117.109.216.in-addr.arpa. (46) (DF)
15:20:06.000311 sprite.wwnet.net.domain > 123.123.123.240.1065: 1560*
1/5/5 (279)
15:20:06.000687 123.123.123.240.1065 > sprite.wwnet.net.domain: 1561+
PTR? 70.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.060732 sprite.wwnet.net.domain > 123.123.123.240.1065: 1561*
1/5/5 (276)
15:20:06.061147 123.123.123.240.1065 > sprite.wwnet.net.domain: 1562+
PTR? 73.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.199215 sprite.wwnet.net.domain > 123.123.123.240.1065: 1562*
1/5/5 (277)
15:20:06.199595 123.123.123.240.1065 > sprite.wwnet.net.domain: 1563+
PTR? 66.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.256277 sprite.wwnet.net.domain > 123.123.123.240.1065: 1563*
1/5/5 (276)
15:20:06.256652 123.123.123.240.1065 > sprite.wwnet.net.domain: 1564+
PTR? 74.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.320372 sprite.wwnet.net.domain > 123.123.123.240.1065: 1564*
1/5/5 (277)
15:20:06.320748 123.123.123.240.1065 > sprite.wwnet.net.domain: 1565+
PTR? 205.117.109.216.in-addr.arpa. (46) (DF)
15:20:06.383390 sprite.wwnet.net.domain > 123.123.123.240.1065: 1565*
1/5/5 (279)
15:20:06.384242 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8969937
0,nop,wscale 0> (DF) [tos 0x10]
15:20:09.375214 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8970237
0,nop,wscale 0> (DF) [tos 0x10]
15:20:15.375192 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8970837
0,nop,wscale 0> (DF) [tos 0x10]
TCPDUMP to DNS SERVER, telnet port 53:
15:28:23.096096 123.123.123.240.1066 > sprite.wwnet.net.domain: 32519+
AAAA? sprite.wwnet.net. (34) (DF)
15:28:23.115363 sprite.wwnet.net.domain > 123.123.123.240.1066: 32519*
0/1/0 (85)
15:28:23.115706 123.123.123.240.1066 > sprite.wwnet.net.domain: 32520+
AAAA? sprite.wwnet.net.localdomain. (46) (DF)
15:28:23.134217 sprite.wwnet.net.domain > 123.123.123.240.1066: 32520
NXDomain 0/1/0 (121)
15:28:23.134782 123.123.123.240.1066 > sprite.wwnet.net.domain: 32521+
A? sprite.wwnet.net. (34) (DF)
15:28:23.154865 sprite.wwnet.net.domain > 123.123.123.240.1066: 32521*
1/2/2 A sprite.wwnet.net (119)
15:28:23.155665 123.123.123.240.1066 > sprite.wwnet.net.domain: 21669+
PTR? 2.211.142.209.in-addr.arpa. (44) (DF)
15:28:23.176607 sprite.wwnet.net.domain > 123.123.123.240.1066: 21669*
1/2/2 (143)
15:28:23.177382 123.123.123.240.3799 > sprite.wwnet.net.domain: S
2259943146:2259943146(0) win 5840 <mss 1460,sackOK,timestamp 9019617
0,nop,wscale 0> (DF) [tos 0x10]
15:28:26.175190 123.123.123.240.3799 > sprite.wwnet.net.domain: S
2259943146:2259943146(0) win 5840 <mss 1460,sackOK,timestamp 9019917
3:12 p.m.
New subject: Network troubleshooting, any experts?
On Wed, 2004-04-28 at 16:03, Elam Daly wrote:
Hi list,
First let me say that the particular server that I am trying to
troubleshoot is not Fedora, but
RedHat 9. As I am subscribed to this list, I thought it would be a good
place to ask.
At this particular company we have a webserver, that sits behind a
firewall/router. All incoming port 80
traffic is directed to this server. All computers in the company reside
internally on 123.123.123.* ip addresses.
All DNS resolution is done externally.
Now the problem is that all computers on the network can browse the
internet and do various chores like
telnet and ssh with no problem, except for the web server. I can ssh,
telnet etc. to other computers on the internal network
from the web server but not to the outside world.
Some oddities:
My resolv.conf file has the ip addresses of my DNS servers. If I ping
an internet address I get back the ip resolution ok, yet I cannot
telnet to either of my DNS servers on port 53 from the web server. So
how am I getting back ip addresses when I ping?
Traceroute and ping respond ok, but no other utilities respond. They
all time out. I ran some tcpdump's telneting to yahoo.com and the DNS
server and I've
included those below if it's helpful to anyone.
I have no firewall running, and just to be sure I've flushed the
iptables and ran the /etc/rc3.d/iptables script with the -stop flag.
I've also talked to the isp( it's their router ) and they claim that if
all the other computers can get web access then so should
the webserver.
If anyone has ANY suggestions it would be most helpful.
Cheers,
Elam Daly
Whiteware Inc.
TCPDUMP to YAHOO.COM telnet port 80:
15:20:05.621044 123.123.123.240.1065 > sprite.wwnet.net.domain: 29834+
AAAA? www.yahoo.com. (31) (DF)
15:20:05.700534 sprite.wwnet.net.domain > 123.123.123.240.1065: 29834
1/1/0 (137)
15:20:05.700874 123.123.123.240.1065 > sprite.wwnet.net.domain: 29835+
A? www.yahoo.com. (31) (DF)
15:20:05.723337 sprite.wwnet.net.domain > 123.123.123.240.1065: 29835
9/9/9 CNAME[|domain]
15:20:05.724132 123.123.123.240.1065 > sprite.wwnet.net.domain: 1558+
PTR? 68.118.109.216.in-addr.arpa. (45) (DF)
15:20:05.830093 sprite.wwnet.net.domain > 123.123.123.240.1065: 1558*
1/5/5 (276)
15:20:05.830519 123.123.123.240.1065 > sprite.wwnet.net.domain: 1559+
PTR? 65.118.109.216.in-addr.arpa. (45) (DF)
15:20:05.893671 sprite.wwnet.net.domain > 123.123.123.240.1065: 1559*
1/5/5 (276)
15:20:05.894048 123.123.123.240.1065 > sprite.wwnet.net.domain: 1560+
PTR? 108.117.109.216.in-addr.arpa. (46) (DF)
15:20:06.000311 sprite.wwnet.net.domain > 123.123.123.240.1065: 1560*
1/5/5 (279)
15:20:06.000687 123.123.123.240.1065 > sprite.wwnet.net.domain: 1561+
PTR? 70.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.060732 sprite.wwnet.net.domain > 123.123.123.240.1065: 1561*
1/5/5 (276)
15:20:06.061147 123.123.123.240.1065 > sprite.wwnet.net.domain: 1562+
PTR? 73.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.199215 sprite.wwnet.net.domain > 123.123.123.240.1065: 1562*
1/5/5 (277)
15:20:06.199595 123.123.123.240.1065 > sprite.wwnet.net.domain: 1563+
PTR? 66.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.256277 sprite.wwnet.net.domain > 123.123.123.240.1065: 1563*
1/5/5 (276)
15:20:06.256652 123.123.123.240.1065 > sprite.wwnet.net.domain: 1564+
PTR? 74.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.320372 sprite.wwnet.net.domain > 123.123.123.240.1065: 1564*
1/5/5 (277)
15:20:06.320748 123.123.123.240.1065 > sprite.wwnet.net.domain: 1565+
PTR? 205.117.109.216.in-addr.arpa. (46) (DF)
15:20:06.383390 sprite.wwnet.net.domain > 123.123.123.240.1065: 1565*
1/5/5 (279)
15:20:06.384242 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8969937
0,nop,wscale 0> (DF) [tos 0x10]
15:20:09.375214 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8970237
0,nop,wscale 0> (DF) [tos 0x10]
15:20:15.375192 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8970837
0,nop,wscale 0> (DF) [tos 0x10]
TCPDUMP to DNS SERVER, telnet port 53:
15:28:23.096096 123.123.123.240.1066 > sprite.wwnet.net.domain: 32519+
AAAA? sprite.wwnet.net. (34) (DF)
15:28:23.115363 sprite.wwnet.net.domain > 123.123.123.240.1066: 32519*
0/1/0 (85)
15:28:23.115706 123.123.123.240.1066 > sprite.wwnet.net.domain: 32520+
AAAA? sprite.wwnet.net.localdomain. (46) (DF)
15:28:23.134217 sprite.wwnet.net.domain > 123.123.123.240.1066: 32520
NXDomain 0/1/0 (121)
15:28:23.134782 123.123.123.240.1066 > sprite.wwnet.net.domain: 32521+
A? sprite.wwnet.net. (34) (DF)
15:28:23.154865 sprite.wwnet.net.domain > 123.123.123.240.1066: 32521*
1/2/2 A sprite.wwnet.net (119)
15:28:23.155665 123.123.123.240.1066 > sprite.wwnet.net.domain: 21669+
PTR? 2.211.142.209.in-addr.arpa. (44) (DF)
15:28:23.176607 sprite.wwnet.net.domain > 123.123.123.240.1066: 21669*
1/2/2 (143)
15:28:23.177382 123.123.123.240.3799 > sprite.wwnet.net.domain: S
2259943146:2259943146(0) win 5840 <mss 1460,sackOK,timestamp 9019617
0,nop,wscale 0> (DF) [tos 0x10]
15:28:26.175190 123.123.123.240.3799 > sprite.wwnet.net.domain: S
2259943146:2259943146(0) win 5840 <mss 1460,sackOK,timestamp 9019917
How about a traceroute to yahoo.com ?
3:17 p.m.
New subject: Network troubleshooting, any experts?
Michael Gargiullo wrote:
How about a traceroute to yahoo.com ?
Howdy,
A Traceroute to yahoo is timing out.
Here's one to slashdot:
1 * 123.123.123.254 (123.123.123.254) 1.453 ms 1.980 ms
2 64.27.222.205 (64.27.222.205) 11.605 ms 11.215 ms 11.632 ms
3 209-254-40-205.ip.mcleodusa.net (209.254.40.205) 27.527 ms 29.637
ms 27.584 ms
4 CHCGILWUH53JC02-SO0-2-0-0.mcleodusa.net (64.198.101.141) 28.712 ms
35.579 ms 27.045 ms
5 CHCGILWUH53JC01-SO0-0-0-0.mcleodusa.net (64.198.101.137) 27.698 ms
26.678 ms 27.445 ms
6 CHCGILDTHBUJC01-SO0-3-0-0.mcleodusa.net (64.198.100.46) 27.583 ms
29.617 ms 27.571 ms
7 sl-st20-chi-5-0.sprintlink.net (144.223.241.1) 27.567 ms 28.564
ms 28.289 ms
8 sl-st21-chi-1-0.sprintlink.net (144.232.8.103) 27.796 ms 27.319
ms 31.206 ms
9 bpr1-so-4-0-0.ChicagoEquinix.savvis.net (208.174.226.65) 27.625 ms
28.061 ms 27.219 ms
10 dcr2-so-4-3-0.Chicago.savvis.net (208.175.10.237) 27.849 ms 27.558
ms 28.846 ms
11 dcr2-loopback.SantaClara.savvis.net (208.172.146.100) 96.232 ms
94.376 ms 94.131 ms
12 bhr1-pos-0-0.SantaClarasc8.savvis.net (208.172.156.198) 86.300 ms
87.093 ms 88.330 ms
13 csr1-ve243.SantaClarasc8.savvis.net (66.35.194.50) 86.390 ms
85.944 ms 85.969 ms
14 66.35.212.174 (66.35.212.174) 88.008 ms 89.670 ms 87.775 ms
15 slashdot.org (66.35.250.150) 85.348 ms 85.311 ms 90.132 ms
~
Elam Daly
Whiteware Inc.
3:32 p.m.
New subject: Network troubleshooting, any experts?
With all (un)due respect, your ISP is probably full of crap. Your tcpdumps
indicate that your UDP connections to the DNS servers are getting through,
at the least. That's why you're able to resolve hostnames. The fact that
your TCP syns never get responded to suggest that they are being blocked
someplace. If the server is not running any firewall as you say, then the
only other logical place is at the border router.
-g
Elam Daly wrote:
Hi list,
First let me say that the particular server that I am trying to
troubleshoot is not Fedora, but
RedHat 9. As I am subscribed to this list, I thought it would be a good
place to ask.
At this particular company we have a webserver, that sits behind a
firewall/router. All incoming port 80
traffic is directed to this server. All computers in the company reside
internally on 123.123.123.* ip addresses.
All DNS resolution is done externally.
Now the problem is that all computers on the network can browse the
internet and do various chores like
telnet and ssh with no problem, except for the web server. I can ssh,
telnet etc. to other computers on the internal network
from the web server but not to the outside world.
Some oddities:
My resolv.conf file has the ip addresses of my DNS servers. If I ping
an internet address I get back the ip resolution ok, yet I cannot
telnet to either of my DNS servers on port 53 from the web server. So
how am I getting back ip addresses when I ping?
Traceroute and ping respond ok, but no other utilities respond. They
all time out. I ran some tcpdump's telneting to yahoo.com and the DNS
server and I've
included those below if it's helpful to anyone.
I have no firewall running, and just to be sure I've flushed the
iptables and ran the /etc/rc3.d/iptables script with the -stop flag.
I've also talked to the isp( it's their router ) and they claim that if
all the other computers can get web access then so should
the webserver.
If anyone has ANY suggestions it would be most helpful.
Cheers,
Elam Daly
Whiteware Inc.
TCPDUMP to YAHOO.COM telnet port 80:
15:20:05.621044 123.123.123.240.1065 > sprite.wwnet.net.domain: 29834+
AAAA? www.yahoo.com. (31) (DF)
15:20:05.700534 sprite.wwnet.net.domain > 123.123.123.240.1065: 29834
1/1/0 (137)
15:20:05.700874 123.123.123.240.1065 > sprite.wwnet.net.domain: 29835+
A? www.yahoo.com. (31) (DF)
15:20:05.723337 sprite.wwnet.net.domain > 123.123.123.240.1065: 29835
9/9/9 CNAME[|domain]
15:20:05.724132 123.123.123.240.1065 > sprite.wwnet.net.domain: 1558+
PTR? 68.118.109.216.in-addr.arpa. (45) (DF)
15:20:05.830093 sprite.wwnet.net.domain > 123.123.123.240.1065: 1558*
1/5/5 (276)
15:20:05.830519 123.123.123.240.1065 > sprite.wwnet.net.domain: 1559+
PTR? 65.118.109.216.in-addr.arpa. (45) (DF)
15:20:05.893671 sprite.wwnet.net.domain > 123.123.123.240.1065: 1559*
1/5/5 (276)
15:20:05.894048 123.123.123.240.1065 > sprite.wwnet.net.domain: 1560+
PTR? 108.117.109.216.in-addr.arpa. (46) (DF)
15:20:06.000311 sprite.wwnet.net.domain > 123.123.123.240.1065: 1560*
1/5/5 (279)
15:20:06.000687 123.123.123.240.1065 > sprite.wwnet.net.domain: 1561+
PTR? 70.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.060732 sprite.wwnet.net.domain > 123.123.123.240.1065: 1561*
1/5/5 (276)
15:20:06.061147 123.123.123.240.1065 > sprite.wwnet.net.domain: 1562+
PTR? 73.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.199215 sprite.wwnet.net.domain > 123.123.123.240.1065: 1562*
1/5/5 (277)
15:20:06.199595 123.123.123.240.1065 > sprite.wwnet.net.domain: 1563+
PTR? 66.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.256277 sprite.wwnet.net.domain > 123.123.123.240.1065: 1563*
1/5/5 (276)
15:20:06.256652 123.123.123.240.1065 > sprite.wwnet.net.domain: 1564+
PTR? 74.118.109.216.in-addr.arpa. (45) (DF)
15:20:06.320372 sprite.wwnet.net.domain > 123.123.123.240.1065: 1564*
1/5/5 (277)
15:20:06.320748 123.123.123.240.1065 > sprite.wwnet.net.domain: 1565+
PTR? 205.117.109.216.in-addr.arpa. (46) (DF)
15:20:06.383390 sprite.wwnet.net.domain > 123.123.123.240.1065: 1565*
1/5/5 (279)
15:20:06.384242 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8969937
0,nop,wscale 0> (DF) [tos 0x10]
15:20:09.375214 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8970237
0,nop,wscale 0> (DF) [tos 0x10]
15:20:15.375192 123.123.123.240.3796 > p5.www.dcn.yahoo.com.http: S
1740721116:1740721116(0) win 5840 <mss 1460,sackOK,timestamp 8970837
0,nop,wscale 0> (DF) [tos 0x10]
TCPDUMP to DNS SERVER, telnet port 53:
15:28:23.096096 123.123.123.240.1066 > sprite.wwnet.net.domain: 32519+
AAAA? sprite.wwnet.net. (34) (DF)
15:28:23.115363 sprite.wwnet.net.domain > 123.123.123.240.1066: 32519*
0/1/0 (85)
15:28:23.115706 123.123.123.240.1066 > sprite.wwnet.net.domain: 32520+
AAAA? sprite.wwnet.net.localdomain. (46) (DF)
15:28:23.134217 sprite.wwnet.net.domain > 123.123.123.240.1066: 32520
NXDomain 0/1/0 (121)
15:28:23.134782 123.123.123.240.1066 > sprite.wwnet.net.domain: 32521+
A? sprite.wwnet.net. (34) (DF)
15:28:23.154865 sprite.wwnet.net.domain > 123.123.123.240.1066: 32521*
1/2/2 A sprite.wwnet.net (119)
15:28:23.155665 123.123.123.240.1066 > sprite.wwnet.net.domain: 21669+
PTR? 2.211.142.209.in-addr.arpa. (44) (DF)
15:28:23.176607 sprite.wwnet.net.domain > 123.123.123.240.1066: 21669*
1/2/2 (143)
15:28:23.177382 123.123.123.240.3799 > sprite.wwnet.net.domain: S
2259943146:2259943146(0) win 5840 <mss 1460,sackOK,timestamp 9019617
0,nop,wscale 0> (DF) [tos 0x10]
15:28:26.175190 123.123.123.240.3799 > sprite.wwnet.net.domain: S
2259943146:2259943146(0) win 5840 <mss 1460,sackOK,timestamp 9019917
--
/------------------------------------------\
| Greg Forte gforte(a)udel.edu |
| IT - User Services 302-831-1982 |
| University of Delaware Newark, DE |
\------------------------------------------/
3:35 p.m.
New subject: Network troubleshooting, any experts?
gforte wrote:
With all (un)due respect, your ISP is probably full of crap. Your
tcpdumps
indicate that your UDP connections to the DNS servers are getting
through,
at the least. That's why you're able to resolve hostnames. The fact
that
your TCP syns never get responded to suggest that they are being blocked
someplace. If the server is not running any firewall as you say, then
the
only other logical place is at the border router.
-g
Does DNS resolve names through UDP? Would that explain why I can't telnet
to port 53 on the DNS servers,yet still get name resolutions? Am I
wrong conceptually
on how DNS works?
Thanks
Elam
3:43 p.m.
New subject: Network troubleshooting, any experts?
Am Mi, den 28.04.2004 schrieb Elam Daly um 22:35:
Does DNS resolve names through UDP? Would that explain why I
can't telnet
to port 53 on the DNS servers,yet still get name resolutions? Am I
wrong conceptually on how DNS works?
Yes, you are wrong and yes, telnet uses TCP. That name resolving uses
UDP on port 53 does not mean you can then block TCP port 53. It must be
open too.
Thanks
Elam
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2188.nptl
Sirendipity 22:40:51 up 1 day, 21:29, load average: 0.21, 0.22, 0.21
[ Γνωθι σ'αυτον - gnothi seauton ]
my life is a planetarium - and you are the stars
4:20 p.m.
New subject: Network troubleshooting, any experts?
At 14:35 4/28/2004, you wrote:
Does DNS resolve names through UDP? Would that explain why I
can't telnet
to port 53 on the DNS servers,yet still get name resolutions? Am I wrong
conceptually
on how DNS works?
DNS resolves queries when possible using UDP, and when the query is too
large for a UDP packet it can also use TCP. So udp/53 and tcp/53 must both
be open in order for DNS to work properly.
Cheers,
--
Rodolfo J. Paiz
rpaiz(a)simpaticus.com
http://www.simpaticus.com
6:08 p.m.
New subject: Network troubleshooting, any experts?
Elam Daly wrote:
gforte wrote:
> With all (un)due respect, your ISP is probably full of crap. Your
> tcpdumps
> indicate that your UDP connections to the DNS servers are getting
> through,
> at the least. That's why you're able to resolve hostnames. The fact
> that
> your TCP syns never get responded to suggest that they are being blocked
> someplace. If the server is not running any firewall as you say,
> then the
> only other logical place is at the border router.
>
> -g
Does DNS resolve names through UDP? Would that explain why I can't
telnet
to port 53 on the DNS servers,yet still get name resolutions? Am I
wrong conceptually
on how DNS works?
Thanks
Elam
YES, and YES
DNS service uses UDP,
Telnet is TCP
However, there still appears to be a TCP block. If you look at
/etc/services you see port 53 is defined as domain for both TCP and UDP.
6:02 p.m.
New subject: Network troubleshooting, any experts?
gforte wrote:
With all (un)due respect, your ISP is probably full of crap. Your
tcpdumps
indicate that your UDP connections to the DNS servers are getting
through,
at the least. That's why you're able to resolve hostnames. The fact
that
your TCP syns never get responded to suggest that they are being blocked
someplace. If the server is not running any firewall as you say, then
the
only other logical place is at the border router.
-g
<snip> I've also talked to the isp( it's their router ) and they
claim that
> if all the other computers can get web access then so should
> the webserver.
My thoughts are that they probably know this is a server, and as such
may have blocked TCP from that particular host IP address.
It appears UDP and ICMP are getting through.
7:27 p.m.
New subject: Network troubleshooting, any experts?
Jeff Vian wrote:
\My thoughts are that they probably know this is a server, and as
such
may have blocked TCP from that particular host IP address.
It appears UDP and ICMP are getting through.
>
They do know it's a web server, as they host our website. If TCP is
being blocked though, how is it possible that can people visit the
website? I realize that http connections come in through port 80, but
the responses from the webserver don't. They leave from the
webserver through any port that apache deems neccessary, correct?
Elam Daly
Whiteware Inc.
7:36 p.m.
New subject: Network troubleshooting, any experts?
At 05:27 PM 4/28/2004, you wrote:
Jeff Vian wrote:
>\My thoughts are that they probably know this is a server, and as such
>may have blocked TCP from that particular host IP address.
>
>It appears UDP and ICMP are getting through.
They do know it's a web server, as they host our website. If TCP is being
blocked though, how is it possible that can people visit the
website? I realize that http connections come in through port 80, but the
responses from the webserver don't. They leave from the
webserver through any port that apache deems neccessary, correct?
Elam Daly
Whiteware Inc.
Elam
As far as I know (and that is very little), most blockings occur on inbound
connections. Thus, if your web-site is listening to port 80, and port 80
is blocked either by you or by your ISP or by your corporation, your out of
luck. Unless, of course, you can convince the blocking agency to unblock
that port to your server.
On the other hand, being behind one of those port-80 blocking ISPs myself
(compounded by having a dynamic IP address and running behind a NAT), I've
simply directed my web server to listen on a high-numbered port. (like
12345), and made sure that the links that point to my server include the
port number. If you need further advice on how to accomplish this act of
black-magic, even with a dynamic address, please ask.
David
8:06 p.m.
New subject: Network troubleshooting, any experts?
On Wed, 2004-04-28 at 20:27, Elam Daly wrote:
Jeff Vian wrote:
> \My thoughts are that they probably know this is a server, and as such
> may have blocked TCP from that particular host IP address.
>
>
> It appears UDP and ICMP are getting through.
>
>>
>
>
They do know it's a web server, as they host our website. If TCP is
being blocked though, how is it possible that can people visit the
website? I realize that http connections come in through port 80, but
the responses from the webserver don't. They leave from the
webserver through any port that apache deems neccessary, correct?
Elam Daly
Whiteware Inc.
Yes the destination port indicates the service being requested.--
jludwig <wralphie(a)comcast.net>
8:09 p.m.
New subject: Network troubleshooting, any experts?
Elam Daly wrote:
Jeff Vian wrote:
> \My thoughts are that they probably know this is a server, and as
> such may have blocked TCP from that particular host IP address.
>
>
> It appears UDP and ICMP are getting through.
>
>>
>
>
They do know it's a web server, as they host our website. If TCP is
being blocked though, how is it possible that can people visit the
website? I realize that http connections come in through port 80, but
the responses from the webserver don't. They leave from the
webserver through any port that apache deems neccessary, correct?
Elam Daly
Whiteware Inc.
IPTABLES does stateful filtering and related connection can be
established while new connections can be blocked. I use this on both
ftp (allowing only port 20) and http (allowing only port 80).
A connection estqablished as a reply to a web browser request is related
and can be allowed without being explicitly allowed by port number..
Any TCP connection that originates from the server is new and easily
blocked.
It may be that they are using a similar firewall rule on this particular
host.
Check how your ISP has the router/firewall configured and make sure they
allow this host outbound connections. (As they apparently do for other
hosts.)
6:30 a.m.
New subject: Network troubleshooting, any experts?
Jeff Vian said:
established while new connections can be blocked. I use this on
both
ftp (allowing only port 20) and http (allowing only port 80).
just to ensure that no green sticks here (new people) get confused, ftp is
21, not 20.
you can check what port and protocol is for what service in /etc/services
-d
-+(duncan brown
-+(duncanbrown(a)linuxadvocate.net
-+(http://www.linuxadvocate.net
() ascii ribbon campaign - against html e-mail
/\ - against microsoft attachments
Blessed is the man who, having nothing to say, abstains from giving wordy
evidence of the fact.
-- George Eliot
6:31 a.m.
New subject: Network troubleshooting, any experts?
Hi!
I'm new here to Fedora, and I have a little question about your always
changing signature:
How did you do that?
Which E-mail-client do you use?
With best regards,
Markus
Am Do, den 29.04.2004 schrieb duncan brown um 13:30:
Jeff Vian said:
> established while new connections can be blocked. I use this on both
> ftp (allowing only port 20) and http (allowing only port 80).
just to ensure that no green sticks here (new people) get confused, ftp is
21, not 20.
you can check what port and protocol is for what service in /etc/services
-d
-+(duncan brown
-+(duncanbrown(a)linuxadvocate.net
-+(http://www.linuxadvocate.net
() ascii ribbon campaign - against html e-mail
/\ - against microsoft attachments
Blessed is the man who, having nothing to say, abstains from giving wordy
evidence of the fact.
-- George Eliot
--
Markus Lumplecker <markus.lumplecker(a)lisec.com>
Lisec Software
7:08 a.m.
New subject: Network troubleshooting, any experts?
Am Do, den 29.04.2004 schrieb duncan brown um 13:30:
Jeff Vian said:
> established while new connections can be blocked. I use this on both
> ftp (allowing only port 20) and http (allowing only port 80).
just to ensure that no green sticks here (new people) get confused, ftp is
21, not 20.
That is not correct, or you are only speaking about passive FTP mode.
Then port 20 and random high ports are participated. In case of active
FTP mode port 20 is used too! See for illustration i.e.
http://slacksite.com/other/ftp.html
you can check what port and protocol is for what service in
/etc/services
$ grep ftp /etc/services
ftp-data 20/tcp
ftp-data 20/udp
ftp 21/tcp
ftp 21/udp fsp fspd
-d
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2188.nptl
Sirendipity 14:04:42 up 2 days, 12:53, load average: 0.77, 0.96, 1.24
[ Γνωθι σ'αυτον - gnothi seauton ]
my life is a planetarium - and you are the stars
8:13 a.m.
New subject: Network troubleshooting, any experts?
duncan brown wrote:
Jeff Vian said:
>established while new connections can be blocked. I use this on both
>ftp (allowing only port 20) and http (allowing only port 80).
>
>
just to ensure that no green sticks here (new people) get confused, ftp is
21, not 20.
you can check what port and protocol is for what service in /etc/services
Sorry , I reversed the data and control ports when I typed that above. :-(
My firewall lists 21 as allowed and only allows 20 as a related connection.
4:04 a.m.
New subject: Network troubleshooting, any experts?
Elam Daly wrote:
Jeff Vian wrote:
> \My thoughts are that they probably know this is a server, and as such
> may have blocked TCP from that particular host IP address.
>
>
> It appears UDP and ICMP are getting through.
>
>>
>
>
They do know it's a web server, as they host our website. If TCP is
being blocked though, how is it possible that can people visit the
website? I realize that http connections come in through port 80, but
the responses from the webserver don't. They leave from the
webserver through any port that apache deems neccessary, correct?
Elam Daly
Whiteware Inc.
Without further info it's hard to say. The output of tcpdump is very cryptic
and hard to read, it's not even differentiating between TCP and UDP. Do you
have ethereal or tethereal installed, it's much, much beter.
The final 3 packets to p5.www.dcn.yahoo.com.http don't show any responses,
and look like retransmissions. My guess would be that the firewall has been
setup to block all incoming TCP traffic to any port other than port 80. If
the firewall isn't stateful that would block all responses to outgoing TCP
connections.
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw(a)ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555
3:39 p.m.
New subject: Network troubleshooting, any experts?
Am Mi, den 28.04.2004 schrieb Elam Daly um 22:03:
Please do not highjack foreign threads. If not intending to reply to a
previous post, do not press reply and erase subject and body and
exchange it with your own. Use a plain fresh new mail. Thank you
Hi list,
First let me say that the particular server that I am trying to
troubleshoot is not Fedora, but
RedHat 9. As I am subscribed to this list, I thought it would be a good
place to ask.
At this particular company we have a webserver, that sits behind a
firewall/router. All incoming port 80
traffic is directed to this server. All computers in the company reside
internally on 123.123.123.* ip addresses.
All DNS resolution is done externally.
Now the problem is that all computers on the network can browse the
internet and do various chores like
telnet and ssh with no problem, except for the web server. I can ssh,
telnet etc. to other computers on the internal network
from the web server but not to the outside world.
Why shall it be possible to access the net from the webserver? Is it not
sufficient if the webserver respond to HTTP request from the net? Or
does even that not work? Then you have a wrong setup with your
firewall/router.
Some oddities:
My resolv.conf file has the ip addresses of my DNS servers. If I ping
an internet address I get back the ip resolution ok, yet I cannot
telnet to either of my DNS servers on port 53 from the web server. So
how am I getting back ip addresses when I ping?
ping is not the mighty master tool for everything. Primary name
resolution uses UDP, not TCP, nor ICMP like ping.
Traceroute and ping respond ok, but no other utilities respond. They
all time out. I ran some tcpdump's telneting to yahoo.com and the DNS
server and I've
included those below if it's helpful to anyone.
Then ICMP traffic is allowed and routed, all other at least partly
blocked.
I have no firewall running, and just to be sure I've flushed the
iptables and ran the /etc/rc3.d/iptables script with the -stop flag.
I've also talked to the isp( it's their router ) and they claim that if
all the other computers can get web access then so should
the webserver.
Check the output of "route", check the firewalling/port forwarding rules
on the firewall/router, be sure the NIC, the cable and the switch port
are ok (no errors in the output of ifconfig).
If anyone has ANY suggestions it would be most helpful.
Cheers,
Elam Daly
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2188.nptl
Sirendipity 22:29:30 up 1 day, 21:18, load average: 0.23, 0.20, 0.23
[ Γνωθι σ'αυτον - gnothi seauton ]
my life is a planetarium - and you are the stars
3:48 p.m.
New subject: Network troubleshooting, any experts?
Alexander Dalloz wrote:
Why shall it be possible to access the net from the webserver? Is it not
sufficient if the webserver respond to HTTP request from the net? Or
does even that not work? Then you have a wrong setup with your
firewall/router.
The webserver responds to http request with no problem.
Check the output of "route", check the firewalling/port forwarding rules
on the firewall/router, be sure the NIC, the cable and the switch port
are ok (no errors in the output of ifconfig).
Output from route:
[root@localhost root]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
123.123.123.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 123.123.123.254 0.0.0.0 UG 0 0 0 eth0
Output from ifconfig:
[root@localhost root]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:4B:27:1E:1A
inet addr:123.123.123.240 Bcast:123.123.123.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83061 errors:83 dropped:0 overruns:0 frame:129
TX packets:37705 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:8443843 (8.0 Mb) TX bytes:8538271 (8.1 Mb)
Interrupt:10 Base address:0x1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1032 errors:0 dropped:0 overruns:0 frame:0
TX packets:1032 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:77868 (76.0 Kb) TX bytes:77868 (76.0 Kb)
I don't have access to the router. It's owned by the ISP and we don't
know the password(It wasn't my idea), so
I am at their mercy for now.
Thanks,
Elam
12:13 a.m.
New subject: Network troubleshooting, any experts?
Wednesday, April 28, 2004 2:04 PM Elam Daly asked:
At this particular company we have a webserver, that sits behind a
firewall/router. All incoming port 80
traffic is directed to this server. All computers in the
company reside
internally on 123.123.123.* ip addresses.
All DNS resolution is done externally.
How did you get the 123.123.123/24 address space assigned to your
network?
According to IANA:
<start clip>
INTERNET PROTOCOL V4 ADDRESS SPACE
(last updated 28 April 2004)
The allocation of Internet Protocol version 4 (IPv4) address space to
various registries is listed here. Originally, all the IPv4 address
spaces was managed directly by the IANA. Later parts of the address
space were allocated to various other registries to manage for
particular purposes or regional areas of the world. RFC 1466 [RFC1466]
documents most of these allocations.
Address
Block Date Registry - Purpose Notes or Reference
----- ------ --------------------------- ------------------
000/8 Sep 81 IANA - Reserved
001/8 Sep 81 IANA - Reserved
002/8 Sep 81 IANA - Reserved
003/8 May 94 General Electric Company
...
122/8 Sep 81 IANA - Reserved
123/8 Sep 81 IANA - Reserved
124/8 Sep 81 IANA - Reserved
125/8 Sep 81 IANA - Reserved
126/8 Sep 81 IANA - Reserved
127/8 Sep 81 IANA - Reserved See [RFC3330]
<end clip>
The 123 address space is clearly a reserved Class A Address.
Are you using NAT? I sincerely hope so. But if so, then why not use one
of the private address spaces? If not, you're lucky you're getting any
traffic back at all.
Now the problem is that all computers on the network can browse the
internet and do various chores like
telnet and ssh with no problem, except for the web server. I
can ssh,
telnet etc. to other computers on the internal network
from the web server but not to the outside world.
For the rest of your network, see above.
For your web server, the question of NAT applies but is compounded by
issues regarding the way your ISP is forwarding the web traffic in their
router.
I have no firewall running, and just to be sure I've flushed the
iptables and ran the /etc/rc3.d/iptables script with the
-stop flag. I've also talked to the isp( it's their router )
and they claim that if
all the other computers can get web access then so should
the webserver.
Now, I have seen cases where ISPs will limit outgoing connections from
known, world accessable servers connected to their network, over which
they have no direct security control. But in this case, I have a gut
feeling that another 123.123.123.240 exists somewhere out there (someone
else using a reserved address) and some of your traffic is just getting
lost. The general purpose router protocols are supposed to keep this
sort of thing from happening, but when unassignigned addresses are added
into the mix, unpredictable things can start popping up (or dropping out
as the case may be.)
Eric Diamond
eDiamond Networking & Security
303-246-9555
eric(a)ediamond.net
12:41 a.m.
New subject: Network troubleshooting, any experts?
lol, he just spoofed his addresses so the list can't see the real ips.
On Sat, 2004-05-01 at 08:13, Eric Diamond wrote:
Wednesday, April 28, 2004 2:04 PM Elam Daly asked:
> At this particular company we have a webserver, that sits behind a
> firewall/router. All incoming port 80
> traffic is directed to this server. All computers in the
> company reside
> internally on 123.123.123.* ip addresses.
> All DNS resolution is done externally.
How did you get the 123.123.123/24 address space assigned to your
network?
According to IANA:
<start clip>
INTERNET PROTOCOL V4 ADDRESS SPACE
(last updated 28 April 2004)
The allocation of Internet Protocol version 4 (IPv4) address space to
various registries is listed here. Originally, all the IPv4 address
spaces was managed directly by the IANA. Later parts of the address
space were allocated to various other registries to manage for
particular purposes or regional areas of the world. RFC 1466 [RFC1466]
documents most of these allocations.
Address
Block Date Registry - Purpose Notes or Reference
----- ------ --------------------------- ------------------
000/8 Sep 81 IANA - Reserved
001/8 Sep 81 IANA - Reserved
002/8 Sep 81 IANA - Reserved
003/8 May 94 General Electric Company
...
122/8 Sep 81 IANA - Reserved
123/8 Sep 81 IANA - Reserved
124/8 Sep 81 IANA - Reserved
125/8 Sep 81 IANA - Reserved
126/8 Sep 81 IANA - Reserved
127/8 Sep 81 IANA - Reserved See [RFC3330]
<end clip>
The 123 address space is clearly a reserved Class A Address.
Are you using NAT? I sincerely hope so. But if so, then why not use one
of the private address spaces? If not, you're lucky you're getting any
traffic back at all.
> Now the problem is that all computers on the network can browse the
> internet and do various chores like
> telnet and ssh with no problem, except for the web server. I
> can ssh,
> telnet etc. to other computers on the internal network
> from the web server but not to the outside world.
For the rest of your network, see above.
For your web server, the question of NAT applies but is compounded by
issues regarding the way your ISP is forwarding the web traffic in their
router.
> I have no firewall running, and just to be sure I've flushed the
> iptables and ran the /etc/rc3.d/iptables script with the
> -stop flag. I've also talked to the isp( it's their router )
> and they claim that if
> all the other computers can get web access then so should
> the webserver.
Now, I have seen cases where ISPs will limit outgoing connections from
known, world accessable servers connected to their network, over which
they have no direct security control. But in this case, I have a gut
feeling that another 123.123.123.240 exists somewhere out there (someone
else using a reserved address) and some of your traffic is just getting
lost. The general purpose router protocols are supposed to keep this
sort of thing from happening, but when unassignigned addresses are added
into the mix, unpredictable things can start popping up (or dropping out
as the case may be.)
Eric Diamond
eDiamond Networking & Security
303-246-9555
eric(a)ediamond.net
--
Rotariu Bogdan <bogdan(a)alterox.ro>
Alterox Sistem
12:06 a.m.
New subject: Network troubleshooting, any experts?
Friday, April 30, 2004 11:41 PM Rotariu Bogdan
lol, he just spoofed his addresses so the list can't see the real
ips.
That's what I thought at first too, but in all his tcp dumps too? I tend
to do a lot of creative editing when posting, but that's just way too
overboard.
Besides, considering he's experiencing what appears to be a routing
issue, we wouldn't be able to give very effective help if he did edit
that data.
Eric Diamond
eDiamond Networking & Security
303-246-9555
eric(a)ediamond.net
1:54 p.m.
On Wed, 2004-04-28 at 11:10, Greg Ennis wrote:
On Wed, 2004-04-28 at 12:14, Taylor, ForrestX wrote:
>
>
> xys:/ is not a Windows share name (or format). You need something like
> //xys/share (//xys/c$ for example).
>
> Forrest
>
>
Forrest,
Thanks very much!!! I used your syntax and it worked. Now I need to
find a way to bypass the password question and I should be home free!!!
Try using the credentials or password option:
//xyz/c$ /mnt/ceb smbfs noauto,user,credentials=/home/user/smbfile 0
0
`man smbmount` for more information.
Forrest
7290
days inactive
7302
days old
35 comments
20 participants
participants (20)
-
Alexander Dalloz -
david -
Don Levey -
duncan brown -
Elam Daly -
Eric Diamond -
Greg Forte -
Gregory P. Ennis -
Jeff Vian -
jludwig -
John Lagrue -
Mac -
Markus Lumplecker -
Michael Gargiullo -
Nigel Wade -
Rick Stevens -
Rodolfo J. Paiz -
Rotariu Bogdan-Stefan -
Taylor, ForrestX -
竜槍騎兵