05-16-2017
Could this be a routing thing? i.e. there is no route out for 192.168.1.0/24
Can you show us the output from netstat -rn?
Perhaps a trace to check that you are actually connecting to the correct 192.168.1.82. It is possible that you are being routed off elsewhere when you try to connect in. What does traceroute 192.168.1.82 give you from the client end? - or tracert 192.168.1.82 on Windows. Is it what you expect and is it similar to trying to get to the other addresses? Perhaps you are being sent elsewhere and it is rightly rejecting your login attempt. You might need to look at ARP tables to make sure you are getting to the right card by checking the MAC address.
Sorry I can't give more help at the moment,
Robin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have been looking for info on how to aggregate 2 ore 3 NIC's into into one big pipe. Any advice would be appreciated.
-Chuck (4 Replies)
Discussion started by: 98_1LE
4 Replies
2. UNIX for Dummies Questions & Answers
I did a netstat -an and saw that ntp was listening on 4 UDP ports for each interface. Is this insecure because they are UDP ports and I don't see them in a listen state, is that because they are just a client.
Thank you.
*.ntp Idle... (2 Replies)
Discussion started by: csross
2 Replies
3. UNIX for Dummies Questions & Answers
Greetings!
I just managed to install Solaris 10 on a Sparc based machine. However, there might be a problem with the way ssh is configured.
I CAN ssh from the machine into another on the network (same subnet, as root), but then the newly installed machine CANNOT seem to accept incoming ssh... (2 Replies)
Discussion started by: agummad
2 Replies
4. Shell Programming and Scripting
Hi!
I have two solaris 10 machines(say 10.1.1.1,10.1.1.2). i have installed rsync on 10.1.1.2,
10.1.1.1:::
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
-bash-3.00$ ssh 10.1.1.2 "echo $PATH"
Password:... (4 Replies)
Discussion started by: dddkiran
4 Replies
5. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
6. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
7. Red Hat
I want to SSH to 192.168.1.15 Server from my machine, my ip was 192.168.1.99
Source Destination was UP, with IP 192.168.1.15.
This is LAN Network there are 30 Machine's Connected to the network and working fine, I'm Playing around the local machine's because I need to apply the same rules in... (2 Replies)
Discussion started by: babinlonston
2 Replies
8. Red Hat
Dear Concern,
I want to block all ports of a particular node (ip: 172.16.10.141) through iptables. My nodes ip addresses are as below:172.16.10.137
172.16.10.138
Please advise us. (0 Replies)
Discussion started by: makauser
0 Replies
9. AIX
Hello Everyone,
Quick question, any short and fast way to locate and map the physical Ethernet ports on the physical server ?
Server with expansion box has around 12 ethernet ports (fibre and ethernet)
what is the quickest way to map or find out en0 represents which physical port ?
... (1 Reply)
Discussion started by: filosophizer
1 Replies
10. UNIX for Beginners Questions & Answers
Hi folks,
I am fairly a beginner when it comes to Solaris OS administration, but part of my job somehow has scope to provide L1-level of OS administration over a few solaris servers.
Now, we have a requirement to limit the number of simultaneous ssh logins/sessions to the server, sort of... (0 Replies)
Discussion started by: engrcha
0 Replies
FINDSMB(1) FINDSMB(1)
NAME
findsmb - list info about machines that respond to SMB name queries on a subnet
SYNOPSIS
findsmb [subnetbroadcastaddress]
DESCRIPTION
This perl script is part of the samba(7) suite.
findsmb is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests.
It uses nmblookup(1) and smbclient(1) to obtain this information.
OPTIONS
-r
Controls whether findsmb takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine. This
option is disabled by default because it is specific to Windows 95 and Windows 95 machines only. If set, nmblookup(1) will be called
with -B option.
subnet broadcast address
Without this option, findsmb will probe the subnet of the machine where findsmb(1) is run. This value is passed to nmblookup(1) as part
of the -B option.
EXAMPLES
The output of findsmb lists the following information for all machines that respond to the initial nmblookup for any name: IP address, Net-
BIOS name, Workgroup name, operating system, and SMB server version.
There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup. There will be an '*' in
front of the workgroup name for machines that are the domain master browser for that workgroup. Machines that are running Windows for Work-
groups, Windows 95 or Windows 98 will not show any information about the operating system or server version.
The command with -r option must be run on a system without nmbd(8) running. If nmbd is running on the system, you will only get the IP
address and the DNS name of the machine. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root
and with -r option on a machine without nmbd running.
For example, running findsmb without -r option set would yield output similar to the following
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.35.10 MINESET-TEST1 [DMVENGR]
192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6]
192.168.35.56 HERBNT2 [HERB-NT]
192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10]
192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX]
192.168.35.78 HERBDHCP1 +[HERB]
192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
VERSION
This man page is correct for version 3.0 of the Samba suite.
SEE ALSO
nmbd(8), smbclient(1), and nmblookup(1)
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open
Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to
DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
FINDSMB(1)