Hello!

I am facing some problem while running my tools (electronics tools).
Actually my company has changed the internet connection (internet provider). Everything is working fine but it changed my IP address (which is ok) but it also changed my HOSTNAME (which is really starnge for me).
And the problem with my tools is that with old connection it's working fine but with new connection GUI mode is not working, only batch mode is working. I am not sure what's the problem.

Can anyone help me on this issue??

Thanks!
Manish

You are going online through a router? Explain a bit. Who is the isp?
get a root terminal open, or put 'sudo' in front of these commands
cat /etc/hosts
cat /etc/resolv.conf
ifconfig
Let us see what they say.

##### cat /etv/hosts #####

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

##### cat /etc/resolv.conf #####

; generated by /sbin/dhclient-script
nameserver 202.149.208.92
nameserver 202.149.208.11

##### ifconfig #####

eth0 Link encap:Ethernet HWaddr 00:1C:C0:BC:F3:45
inet addr:192.168.1.34 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21c:c0ff:febc:f345/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:614971 errors:0 dropped:0 overruns:0 frame:0
TX packets:338329 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:881117673 (840.2 MiB) TX bytes:27405699 (26.1 MiB)
Interrupt:177 Base address:0xe000

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:66887 errors:0 dropped:0 overruns:0 frame:0
TX packets:66887 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:87632659 (83.5 MiB) TX bytes:87632659 (83.5 MiB)

Okay - that all looks good. You're online with NOC in India·

I was in electronics, too, but all the jobs here went over your way because the costs were lower :-(. I gather you have dhcpcd or dhclient running, and have an address from the router. Everything should work.

So, possibilities suggest themselves:
1. Your new isp might not be as well connected as your old one
2. There may be dns or firewall issues causing you to trip over your own shoelaces.
3. The box could be trying ipv6 access and falling over. God help us all when that comes in.

Try a ping and a traceroute to Whatever sites your electronics tools access from both isps. You should be able to do the following for any site (I've used my internal home network in the example)

ping -c2 www.chateau.dec #should ping it twice
nslookup www.chateau.dec # hopefully returns an ipv4 ip e.g. 128.128.128.128
traceroute 128.128.128.128 > file


Then compare the 2 files, and you'll see where the problem is.

Hi...

Actually I am not accessing my tolls from any website but it is from my License Server which has Ip Address 192.168.1.2.

These are the outputs of the commands which you have mentioned:

#### ping -c2 192.168.1.2 #####

PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=0.099 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=0.094 ms

--- 192.168.1.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.094/0.096/0.099/0.010 ms


#### nslookup 192.168.1.2 #####

Server: 202.149.208.11
Address: 202.149.208.11#53

** server can't find 2.1.168.192.in-addr.arpa: NXDOMAIN


##### traceroute 192.168.1.2 #####

traceroute to 202.149.208.11 (202.149.208.11), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Thanks!
Manish

192.168.anything is an internal network number. Those numbers are reserved for internal network use. You certainly threw me talking of isps when your access is actually inhouse!

At any rate, you can see those numbers. So your network connection seems fine. It's the search stuff we can fix

nslookup will be meaningless. The traceroute shows the problem - your box doesn't know where 192.168.1.2 is! Lazy way out is to use /etc/hosts, which at one time had entries for every box on the 'net before dns (back in the 70s) Get the hostname for 192.168.1.2 and add this line to /etc/hosts

192.168.1.2 ThatHost.yourdomain.com ThatHost

try that and let us know. BTW, out of professional curiosity, what software do you run for electronics?