Problem: Solaris 10 to Windows XP Connectivity

UNIX Solaris
1

:wall:
Hello Solaris Users. Although a fundamental skill I am still new to connecting computers together in order that they can see each other, ie. via ping-ing of IP's and/or hostnames.

I wish to install Oracle 10g database on Sun Blade 1500 and access this from Windows XP laptop (running Oracle client), for learning purposes.

I have made entries in the hosts files, eg:

%SystemRoot%\system32\drivers\etc\hosts on XP

and

/etc/hosts on Solaris 10,

of the respective IP addresses and names of each of the two systems, but with
no outcome. Both machines are connected to the same 10/100 Fast Ethernet switch.

If anyone could offer me the solution it would be very helpful (and any other necessary info regarding a Windows XP to Oracle 10g/Solaris 10 setup).

Many thanks,
patcom

2

What exactly is the network arrangement?

What are their IP addresses?

3

Hi Corona688,

Thanks for responding so soon.

XP (from ipconfig command):
Windows IP Configuration

Ethernet adapter Local Area Connection:

                     IP Address ................................:  10.25.80.31
                     Subnet Mask .............................:  255.255.255.0
                     Default Gateway ........................:  10.25.80.254

Solaris 10 (various commands):
bash-3.2#
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
inet 10.25.80.36 netmask ffffff00 broadcast 10.25.80.255
ether 0:3:ba:d9:a0:56
bash-3.2#
bash-3.2#
bash-3.2# routeadm
Configuration Current Current
Option Configuration System State
---------------------------------------------------------------
IPv4 routing disabled disabled
IPv6 routing disabled disabled
IPv4 forwarding disabled disabled
IPv6 forwarding disabled disabled

       Routing services   "route:default ripng:default"

Routing daemons:

                  STATE   FMRI
               disabled   svc:/network/routing/legacy-routing:ipv4
               disabled   svc:/network/routing/legacy-routing:ipv6
               disabled   svc:/network/routing/ndp:default
               disabled   svc:/network/routing/rdisc:default
               disabled   svc:/network/routing/ripng:default
               disabled   svc:/network/routing/ripng:quagga
               disabled   svc:/network/routing/route:default
               disabled   svc:/network/routing/zebra:quagga
               disabled   svc:/network/routing/rip:quagga
               disabled   svc:/network/routing/ospf:quagga
               disabled   svc:/network/routing/ospf6:quagga
               disabled   svc:/network/routing/bgp:quagga

bash-3.2#
bash-3.2#
bash-3.2# netstat -rn

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ---------- ---------
default 10.25.80.254 UG 1 0 bge0
10.25.80.0 10.25.80.36 U 1 1 bge0
224.0.0.0 10.25.80.36 U 1 0 bge0
127.0.0.1 127.0.0.1 UH 1 124 lo0
bash-3.2#
bash-3.2#
bash-3.2# ping 10.25.80.254
no answer from 10.25.80.254
bash-3.2#
bash-3.2#
bash-3.2#

I'm assuming that 10.25.80.254 (showing as Default Gateway on both computers) is the IP of the switch.
Thanks for your time with this,
patcom :b::b::b:

4

switches are switches, not routers; they have no IP and do nothing but switch traffic based on MAC addresses.

I don't know where the 254 came from. That's not invalid exactly, but not a common value for a gateway. What's your router?

Can your windows machine ping the IP address of your solaris machine?

You won't be able to ping the windows machine, because windows doesn't answer ping these days.

5

Windows XP does answer pings (I just tried it). You need to turn on routing in the Solaris box so it can route to the Windows box.
svcadm enable svc:/network/routing/route:default
and make sure svc:/network/routing-setup is online.

6

Windows XP does answer pings only if configured to. Windows and most third party firewalls disable it by default.

*.*..254 is a valid router IP address, and probably the most common after *.*..1 on /24 networks, but it doesn't matter here anyway.

Both machines are on the same subnetwork so routing isn't involved. Enabling the routing service on the Solaris side isn't going to have any effect on this ping issue.