LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 06-01-2009, 06:30 AM   #16
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15

It says :
command not found
 
Old 06-01-2009, 06:35 AM   #17
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
-bash: dig:command not found
 
Old 06-01-2009, 06:37 AM   #18
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
try
Code:
nslookup whatever.that.link.was
instead

If that doesn't work, try ping.
 
Old 06-01-2009, 07:08 AM   #19
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
I get this message:
-bash: nslookup:command not found
and I can't ping the ip of proxy server.
 
Old 06-01-2009, 07:10 AM   #20
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
You're not helping a lot here. Give exact messages.
 
Old 06-01-2009, 07:26 AM   #21
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
ok! I typed this :
nslookup 210.12.0.14
and I got:
-bash: nslookup:command not found
so I typed ping 210.12.0.14
and I got this:
PING 210.12.0.14 (210.12.0.14) 56(84) bytes of data
and nothing more and that's because we can't ping the proxy server of our company.
thanks for your help
 
Old 06-01-2009, 08:14 AM   #22
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
What should I do now? Was the message clear?
I can't ping IP:210.12.0.14 and I can't use dig nor nslookup.
what do you suggest now?
 
Old 06-01-2009, 04:28 PM   #23
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
Sounds like you have a basic networking issue.

Can you show

#ifconfig

#route

#iptables -L

What type of VM are you using? Did you follow all the instructions to enable external connections (bridging, etc.)?

Last edited by billymayday; 06-01-2009 at 05:10 PM.
 
Old 06-02-2009, 01:15 AM   #24
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
I use VMWare workstation 6.5.0 Build 118166 and I followed the instructions on http://richard.gluga.com/search/label/NTLM and we have a proxy server here but we don't have a domain and I'm in a work group but although I typed the name of work group instead of domain it gave me the same error.Should I use different settings ?Here is my server.conf:

#========================================================================
[GENERAL]

LISTEN_PORT:3128

# If you want APS to authenticate you at WWW servers using NTLM then just leave this
# value blank like PARENT_PROXY: and APS will connect to web servers directly.
# You can specify more than one proxy by leaving a space between each one, and
# APS will detect when one fails and automatically fail-over to the next. EG:
#PARENT_PROXY:first_proxy second_proxy third_proxy
# And NOTE that NTLM cannot pass through another proxy server.
PARENT_PROXYroxy.companyname.com

PARENT_PROXY_PORT:3128

# APS will poll the upstream proxy and attempt to fail-over to a new one if it doesn't
# get a response within an appropriate time frame. The amount of time that it will
# wait for a response before attempting fail-over is specified, in seconds, below:
PARENT_PROXY_TIMEOUT:15

# Set to 1 if you want to grant this authorization service to clients from other computers.
# NOTE: all the users from other hosts that will be using you copy of APS for authentication
# will be using your credentials in NTLM auth at the remote host.
ALLOW_EXTERNAL_CLIENTS:0

# If you want to allow some other but not all computers to use your proxy for authorization,
# just set ALLOW_EXTERNAL_CLIENTS:0 and put friendly IP addresses here.
# Use space as a delimiter.
# NOTE that special addesses don't work here (192.168.3.0 for example).
FRIENDLY_IPS:

# Requested URLs are written to "url.log" file. May be useful.
URL_LOG:0

# When a network service listens for connections, there is a maximum number of connection
# attempts to that service that the underlying OS will allow to backlog waiting for a response
# before the OS will start dropping new connection attempts with 'Connection refused'. The
# standard method of determining the maximum number of backlogged connections is to use the
# SOMAXCONN constant, which is supposed to represent the maximum number that an OS will support
# (for example, 5 on Windows 2000 Pro, and 200 on Windows 2000 server). However, because this
# is a statically compiled value in a Python distribution, usually this instead represents the
# the most conservative value (5 on all Windows platforms, and 128 on the GNU/Linux variant I
# tried). So if you are running (for example) a massively threaded/parallel download manager,
# the default value of, say, 5, or whatever SOMAXCONN happens to be set to, may be too low and
# cause some connections to fail. The value below can be set to any integer (it seems that
# Python just silently caps values above the hard limit for the underlying platform), or it can
# be set to the special value of SOMAXCONN (i.e. MAX_CONNECTION_BACKLOG:SOMAXCONN), to use
# whatever this value happens to be set to in your Python build. Setting this higher than
# necessary may cause APS to consume more memory than you needed to.
MAX_CONNECTION_BACKLOG:5

#========================================================================
[CLIENT_HEADER]

# This section describes what and how the server should change in the clients headers.
# Made in order to prevent parent proxy from seeing that you are using wget instead of IE5.5

Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */*
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

# for windows 2000 emulation
# User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT5)

# You can uncomment these chages in client's header to mimic IE5+ better, but in this case
# you may expirience problems with *.html if your client does not really handle compression.
#Accept-Encoding: gzip, deflate

#========================================================================
[NTLM_AUTH]

# Optional value, if leaved blank then APS will use gethostname() to determine
# host's name.
# NOTE1: If you Linux host name differs from Windows host name then it may be that
# MS server wont recognize you host at all and wont grant you access
# to resources requested. Then you have to use this option and APS will use
# this name in NTLM negotiations.
# NOTE2: There are several reports that you can successfully use "foreign" host name
# here. Say, if user may access a resource from 'host1' and may not from 'host2'
# then there is a chance that APS running on 'host2' with NT_HOSTNAME:host1 will
# be able to be granted access to the restricted resource. However use this on
# you own risk as such a trick may be considered as a hack or something.
NT_HOSTNAME:

# Windows Domain.
# NOTE: it is not full qualified internet domain, but windows network domain.
NT_DOMAINroxy.companyname.com
# What user's name to use during authorization. It may differ form real current username.
# If you enable NTLM_TO_BASIC, below, you can either leave this blank or simply
# hash it out.
USER:user

# Password. Just leave it blank here and server will request it at the start time,
# or, if you enable NTLM_TO_BASIC, below, you can either leave this blank or simply
# hash it out, and you *won't* be prompted for a password at start time.
PASSWORDassword

# These two options replace old FULL_NTLM option.
# NTLM authentication consists virtually of two parts: LM and NT. Windows95/98 use
# only LM part, WindowsNT/2000 can use NT and LM or just NT part.
# Almost always using just LM part will be enough. I had several reports
# about LM and NT requirement and no about just NT.
# So try to setup 1, 1 only if you have enough reasons to do so and when you understand
# what you are doing.
# 0, 0 is an illegal combination
# NOTE: if you change these options then you have to setup flag option accordingly.
LM_PART:1
NT_PART:0

# Highly experimental option. See research.txt for details.
# LM - 06820000
# NT - 05820000
# LM + NT - 07820000
NTLM_FLAGS: 06820000

# This option makes APS try to translate NTLM authentication to very usual "Basic"
# scheme. Almost all http clients know it. With this option set to 1 user will be requested
# by his browser to enter his credentials and these username and password will be used by
# APS for NTLM authentication at MS Proxy server or Web server.
# In such a case different users can use one runnig APS with their own credentials.
# NOTE1: currently translation works so it allows only one try for entering
# username/password. If you make a mistake you will have to restart you browser.
# NOTE2: With debug:1 basic username/password will be written in log file in clear
# text format. I could try hide it, but the basic scheme is so weak that anybody
# who had access to APS would be able to get it.
NTLM_TO_BASIC:0

#========================================================================
[DEBUG]

# Set this to 1 if you want to see debug info in many log files. One per connection.
DEBUG:0

# Set this to 1 to get even more debug info.
BIN_DEBUG:0

# Set this to 1 to see some strange activity on screen. Actually you won't want it.
SCR_DEBUG:0

# Not actually a debug option but gives you some details on authentication process
# into *.auth logs. Also see research.txt.
AUTH_DEBUG:0




#ifconfig:
th0 Link encap:Ethernet HWaddr 00:0C:29:B5:2A:81
inet addr:210.12.0.189 Bcast:210.12.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feb5:2a81/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4099 errors:0 dropped:0 overruns:0 frame:0
TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:364795 (356.2 KiB) TX bytes:7362 (7.1 KiB)
Interrupt:67 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:218 errors:0 dropped:0 overruns:0 frame:0
TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16761 (16.3 KiB) TX bytes:16761 (16.3 KiB)

#route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
210.12.0.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 210.12.0.14 0.0.0.0 UG 0 0 0 eth0

#iptables -L:
hain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
 
Old 06-02-2009, 09:19 AM   #25
ngiamol
Member
 
Registered: Apr 2009
Location: Athens - Hellas (greece)
Distribution: Centos
Posts: 36

Rep: Reputation: 16
When i had a similar problem, the NIC was down. For a strange reason after a full update in CentOS, the drivers for my nic was corrupted. Type ifconfig eth0 and see the results.
 
Old 06-03-2009, 12:29 AM   #26
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
Centos gives me this message when I type the command ifconfig eth0:

eth0 Link encap:Ethernet HWaddr 00:0C:29:B5:2A:81
inet addr:210.12.0.189 Bcast:210.12.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feb5:2a81/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1078 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:105460 (102.9 KiB) TX bytes:2960 (2.8 KiB)
Interrupt:67 Base address:0x2000

what does this mean?
 
Old 06-03-2009, 12:33 AM   #27
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
CentOS shows me this message when I type ifconfig eth0 :

eth0 Link encap:Ethernet HWaddr 00:0C:29:B5:2A:81
inet addr:210.12.0.189 Bcast:210.12.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feb5:2a81/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1078 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:105460 (102.9 KiB) TX bytes:2960 (2.8 KiB)
Interrupt:67 Base address:0x2000


what does this mean?
 
Old 06-03-2009, 12:34 AM   #28
reyhaneh.emi
LQ Newbie
 
Registered: May 2009
Location: Iran,Tehran
Posts: 24

Original Poster
Rep: Reputation: 15
CentOS shows me this message when I type ifconfig eth0 :

eth0 Link encap:Ethernet HWaddr 00:0C:29:B5:2A:81
inet addr:210.12.0.189 Bcast:210.12.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:feb5:2a81/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1078 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:105460 (102.9 KiB) TX bytes:2960 (2.8 KiB)
Interrupt:67 Base address:0x2000


what does this mean?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Yum Update error mzizana Linux - Software 2 02-13-2008 07:08 AM
Yum Update error rsreekumar Linux - Software 1 06-18-2007 08:10 PM
Yum on FC6. 'yum update' error. mufy Fedora 8 06-14-2007 03:03 AM
Why this error when trying to do a yum update? oldjoe Fedora 33 11-20-2006 12:22 AM
Yum Update error fcoutel Red Hat 1 12-30-2004 10:22 AM


All times are GMT -5. The time now is 07:39 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration