I'm a total novice as far as networking goes so this may be a stupid question.

In the company where i work they have just installed some new machines in a class A network:

10.1.10.x

I am running debian with a static IP, this is my configuration in /etc/network/interfaces

iface eth0 inet static
address 193.106.32.232
netmask 255.255.255.0
network 193.106.32.0
broadcast 193.106.32.255
gateway 193.106.32.254
dns-nameservers 213.139.0.51 213.139.0.52

The people who i work with all run windows and did not have to make any changes to ping the new network.

What do i have to change to be able to see the new network, connect via samba etc.

All help gratefully appreciated.

-Andy






_____________________________________
“Great works are performed, not by strength, but by perseverance.”
“Marriage is a three rings circus: engagement rings , wedding rings and sufferings.”

Andy,

10.1.10.x is indicative of a class C network (where x can = 0 - 255) not a class A network.

The 10.1.10.x network is not in your subnet so traffic destined to that network would be sent to your default gateway.

Do the windows systems use static IP settings, or are they receiving their information via a DHCP server?

Are the other systems that are able to ping to the 10.1.10.x network on the same subnet as you?
that would mean their systems have an IP in the 193.106.32.0-255 range with a subnet of 255.255.255.0.

Do they use the same gateway as you?

With that information we could probably narrow down the possibilities of what might be causing your troubles.

At this point it could be:

Systems that can communicate with 10.1.10.x are actually on different subnets or use a different gateway that knows how to reach 10.1.10.x while your gateway does not.

Firewalling: System Admin has allowed only certain machines to access the 10.1.10.x network; Your system is not one of them.

Numerous other, but less likely issues.

An idea would be to post a comparison between the IP information and the routing tables on a box that can ping that network vs. your box.

some output comparisons (working system vs. your system) that would be helpful:

ifconifg/ipconfig
route -n
ping -c 5 10.1.10.x (where x = a valid host, no need for -c on the windows box)
tracepath/tracert to 10.1.10.x (where x = a valid host)

Once you can successfully communicate with the network, then start looking at Samba. You must solve your problem from the bottom layers and work your way up.