Ok frustrated with myself for not being able to figure this out and not knowing witch way to proceed.
I was very glad to discover "vimtutor" definitely the best tutorial I've came across in linux so far.
This is what I've set up so far, following a How-to on LinuxSelfHelp

I can ping both directions as long as my firewalls are disabled, I have decided to work on the firewalls problem separately If possible as I was confusing the bejesus out of myself, and possibly any one else who is kind enough to help me out!
If I have to work on the firewalls problem and Nfs setup at the same time let me know, but I hope not.
To put it another way, if I cant get NFS going, then I don't have a firewall problem.

hosts.allow
service: 192.168.1.1
lockd: 192.168.1.1
rquotad: 192.168.1.1
mounted: 192.168.1.1
statd:m 192.168.1.1

hosts.deny
rquotad:ALL
mounted:ALL
statd:ALL
lockd:ALL
portmap:ALL

/etc/exports says:
/home/teabear/Documents 192.168.1.1(no_root_squash,ro)
I chose no_root_squash after failing without it for a while,thinking adding it temporarily,for the purpose of testing might help me get connected easier. --? Is that a major no no?

This is from server
[root@localhost etc]# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 758 status
100024 1 tcp 761 status
100004 2 udp 773 ypserv
100004 1 udp 773 ypserv
100004 2 tcp 776 ypserv
100004 1 tcp 776 ypserv
600100069 1 udp 705 fypxfrd
600100069 1 tcp 707 fypxfrd
391002 2 tcp 32768 sgi_fam
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 32770 nlockmgr
100021 3 udp 32770 nlockmgr
100021 4 udp 32770 nlockmgr
100021 1 tcp 32769 nlockmgr
100021 3 tcp 32769 nlockmgr
100021 4 tcp 32769 nlockmgr
100005 1 udp 735 mountd
100005 1 tcp 738 mountd
100005 2 udp 735 mountd
100005 2 tcp 738 mountd
100005 3 udp 735 mountd
100005 3 tcp 738 mountd
100009 1 udp 752 yppasswdd
[root@localhost etc]#

portmapper,lockd, statd are running on client also.

When I try to mount with the following command: "mount 192.168.1.2:/home/teabear/Documents /mnt" I get the following error:
"failed, reason given by server: Permission denied"
The How-to I'm following says if I get a "failed, reason given by server: Permission denied" error, then I should check the following things.

Quote:
Check your /etc/exports file and make sure that the volume is exported and that your client has the right kind of access to it. For example, if a client only has read access then you have to mount the volume with the ro option rather than the rw option.
End Quote

Does this mean that while I'm at a console on the client, preparing to type in a mount command, I may need to pass in (ro) at that time along with the mount command?

Quote:
Be sure to type exportfs -ra to be extra certain that the exports are being re-read.
End Quote
Did That.

Quote:
Check the file /proc/fs/nfs/exports and make sure the volume and client are listed correctly. (You can also look at the file /var/lib/nfs/xtab for an unabridged list of how all the active export options are set.) If they are not, then you have not re-exported properly.
End Quote

/proc/fs/nfs/exports says:
# Version 1.1
# Path Client(Flags) # IPs
/home/teabear/Documents 192.168.1.2(ro,no_root_squash,sync,wdelay) # 192.168.1.2

var/libs/nfs/xtab is empty <--?Is xtab critical, the impression I get from the above Quote is that I can look at it if I want to or not?

Quote:
If they are listed, make sure the server recognizes your client as being the machine you think it is. For example, you may have an old listing for the client in /etc/hosts that is throwing off the server, or you may not have listed the client's complete address and it may be resolving to a machine in a different domain. Try to ping the client from the server, and try to ping the server from the client. If this doesn't work, or if there is packet loss, you may have lower-level network problems.
End Quote

/etc/hosts says 127.0.0.1 localhost <--?This doesn't seem like the right thing to me, but what say you?

I can ping both directions as long as my firewalls are disabled, I have decided to work on the firewalls problem separately If possible as I was confusing the bejesus out of myself, and possibly any one else who has been kind enough to help me out!
If I have to work on the firewalls problem and Nfs setup at the same time let me know, but I hope not.

continued gratitude to all those who help us newbies.

When someone has a chance, please look at where I'm at with nfs and try to evaluate.
I know its wordy but I wanted you to see I am trying to follow directions in How-to.

Continued gratitude to all those who help us newbies.

Bump.
No rush, I just dont want to get lost somewhere back on page 38.
continued gratitude to all those who help us newbies.

Never mind,
I just got nfs going.
Extreme Newbie mistake in basic configuration.
Only took me three days to find.
Yeah.
I'm off to try to figure out my firewall / iptables

Continued gratitude to all those who help us newbies.