[SOLVED] Share Problem

[Just17]

I had a share set up from my main PC (XPS) using NFS and autofs.
All worked perfectly for a long time.

Well it all worked until I changed the router to which the PC is connected  

The first router issued IP addys in the 192.168.1.xxx  range
The new one uses  192.168.3.xxx

No problem for most things .....  except this share which will not share any more!  

This is the interesting bit .........

$ showmount
Hosts on XPS:
192.168.1.132

It seems the old IP address is held somewhere and is being used for the share.

I cannot find where  

I have checked hosts files and other related files to try to find an entry .....  but no luck.

Does anyone have an idea where this 192.168.1.132 might be held?

The present IP address of the PC is   192.168.3.12

[ghostbunny]

just an idea, did you try to set up a static ip? i did so with my main pc to synchronize via ssh + rsync with my laptop.

if you try it you have to restart i think 

[muungwana]

you can look at the router configuration page,there should be an option somewhere in there to change the local network address.

[pags]

Well...if you want to brute force the answer...

Code: [Select]

grep -r 192.168.1.132 /*

That might take a while (depending on how much stuff you have), but it will look in every file in your system, and report what files have that IP address in them...

[Just17]

you can look at the router configuration page,there should be an option somewhere in there to change the local network address.

I don't wish to change the router's range of addresses ...... it has its own unique range in the area so there is no interference with other routers.

What I wish to do is to change the PC which appears to be insisting on retaining its old IP address for the share ......  IF I am reading the showmount output correctly.

just an idea, did you try to set up a static ip? i did so with my main pc to synchronize via ssh + rsync with my laptop.

if you try it you have to restart i think  

The IP address is in a different range to that which it had been using .....  whether it changes between boots or not, it will still be in the same range issued from the new router connection.


The problem appears to me that it is not sharing on the correct IP address, and I cannot seem to find how to correct it.

It seems to be using the old address from when it was set up on the previous router, and not the new address issued by the new connection.

[Just17]

I am going to have to forget about this .....  pretend it does not happen 

I have set up the shares again on server (XPS) and client and am able to connect again.

The weird IP address still shows on XPS though - bear in mind XPS machine has an IP address of
192.168.3.12 and the only other PC on the network at the moment is  192.168.3.13, so this 192.168.1.132 does not exist .....  although it did a short time ago. The whole network and PCs have been switched off since.

Code: [Select]

[root@XPS user]# showmount
Hosts on XPS:
192.168.1.132
[root@XPS user]#

I just hate it when something like this happens ......  essentially a mount point that appears to not be deleted ......

Oh well, unless someone comes up with an idea where this might be hiding, I will try to forget it.

Thanks for your interest guys

[Just17]

Well...if you want to brute force the answer...

Code: [Select]

grep -r 192.168.1.132 /*

That might take a while (depending on how much stuff you have), but it will look in every file in your system, and report what files have that IP address in them...

It found nothing unfortunately 

[xr200]

WIld guess, what does /var/lib/nfs/rmtab look like?

xr200

[Just17]

WIld guess, what does /var/lib/nfs/rmtab look like?

xr200

Forgot to come back to update this thread .....  sorry.

I was pointed to that file last night .....  very late, so did not return to the forum.

Yes you are correct .....  there was a mount point remaining there that I deleted and rebooted, and all is well.

Thanks for all the input.

Case solved 

[xr200]

Why didn't the suggested grep command find the stale link in rmtab?

Just wondering, seems like it should have worked for you.

xr200

[pags]

Why didn't the suggested grep command find the stale link in rmtab?

Just wondering, seems like it should have worked for you.

xr200

+1

I did a quick test here, and it seems to work...

Is reading to that file restricted?  Perhaps it was run as an un-privileged user...

<EDIT>

Doesn't seem to be...

Code: [Select]

[jpaglia@paglia-e6500 ~]$ ls -l /var/lib/nfs/rmtab
-rw-r--r-- 1 root root 0 Jun  8  2011 /var/lib/nfs/rmtab
[jpaglia@paglia-e6500 ~]$


[Just17]

I wondered that myself .....  but too late to be sure of anything now as I have edited the file myself.

I at first ran the grep command as user .....  but after I got nil results ran it again as root, thinking a file might not allow a user to read it .......  yet it did not find the entry for some reason