fms007
join:2009-05-24
| reply to fms007
Re: VPN Connection
Already bridged both Server and Client and manually configured ips
The username and password for both PCs server and client should be one only meaning
Server PC
Username:SERVER
PASSWORD*****
Client PC
Username:SERVER
PASSWORD*****
On Server PC Bridged TCP/IP Properties i have manually put
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :192.168.1.1
DNS Servers . . . . . . . . . . . : 215.239.204.280
215.239.225.138
On Client PC Bridged TCP/IP Properties i have manually put
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . .: 192.168.1.1
DNS Servers . . . . . . . . . . .: 215.239.204.280
215.239.225.138
Okay....sorry to keep you waiting..goodnight will inform you of the results 2mrw |
|
fms007
join:2009-05-24
2 edits | reply to fms007
Perfect....both the PCs are working perfectly after the network bridge....i am able to access internet via both PCs and can access files from one PC to another and vice versa...will try to access the files via LAN after i put off the router, but right now am able to access the files with the router on....but i think it should work with the router off too...will inform....also will inform by running only one PC at a time and router on...as to the accessing of the internet...but its obvious i m in good hands...thanxs
One more issue also looks like may have got resolved.....
B4 i couldnt open the modem config page if the SERVER LAN ethernet adapter was enabled.....i was forced to disable this SERVER LAN ethernet adapter to get to the modem settings page....but now in bridged condition this issue also looks liked resolved, as i dont have to disable anything and the page opens up on the webrowser.
IPConfig Server
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Network Bridge:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 00-1B-B0-17-AA-BG
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 215.239.204.280
215.239.225.138
IPConfig Client
Windows IP Configuration
Host Name . . . . . . . . . . . . : CLIENT
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Network Bridge:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 00-0H-2E-82-C1-E7
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 215.239.204.280
215.239.225.138
These are the ip config results after network bridge of both Server and Client......i have also changed the username for both PCs to one and the same...ie both are now called SERVER and both have same password.
The only query which i had was why is the IPConfig of Client showing the name
quote:
Windows IP Configuration
Host Name . . . . . . . . . . . . : CLIENT
Primary Dns Suffix . . . . . . . :
This word CLIENT refers to the computer name....i have changed the windows username to SERVER for both computers.....
My question is should i leave the computer name as CLIENT or should i also change it in the registry settings
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName
to SERVER (this i m asking for the computer named Client, PC2)...meaning if i change the name to SERVER will there be a conflict bcos there already is a computer named SERVER in the LAN (ie the first computer,PC1) and there cant be 2 computers with the same name....
If this query of mine is irrelevant than do not bother about it....
I have till now not done anything extra from my side
Will wait for your futher advice... |
|
JamesLevinworth
@embarqhsd.net
| Hey, sorry to keep you hanging here... I've been putting out a fire all this morning. I should be done in about an hour. I'll swing back then.
Glad to read everything works good. How did your test to do with the router off?
Don't worry about the CLIENT host name. This is different than the username you assigned before (SERVER). The Host name names the connection on that PC and needs to be different for both SERVER and CLIENT or, as you guessed, you'll have a conflict. The host name is assigned using the netbois computer name by default(if I remember right) when you setup the networking. These actually can be changed to be different but you don't want them to be. Double check your machine names are consistent (SERVER or CLIENT for each). Go to System properties (windows key+break key), computer name tab and confirm. If not we'll fix this.
ok, I'll be back.... |
|
fms007
join:2009-05-24
1 edit | Hi....i hope no damage from the fire....
It worked perfect with the router off....both PCs also connect to the net independently. Checked in system properties... computer tab...
SERVER
Computer Name:Server
Username:Server
CLIENT
Computer Name:Client
Username:Server
After this i ran the test with RDP
(1.)Port forwarded registry settg....54120
(2.)Port forwarded router RDP-54120......54120
(3.)Disabled Outpost on server and client
(4.)Enabled Windows Firewall on server and client
(5.)Added exception to windows firewall on server for RDP-54120 and confirmed the rule had been added in exception list.
(5.)Configured RDP client on Client (ie select Modem 28.8.... uncheck printers/clipboard....save as)
The test results
LAN results with router OFF
(1.)Possible to connect by typing SERVER:54120 via LAN with router off.
(2.)Possible to connect by typing 192.168.1.2:54120 via LAN with router off
Hence possible by typing IP address as well as name (ie SERVER) via LAN.
WAN results with router ON
(1.)Not possible to connect by typing yourdyndnsname.dyndns.org via WAN with router ON
(2.)Not possible to connect by typing WAN IP address 69.96.3.123 via WAN with router ON
(3.)Not possible to connect by typing WAN IP address 69.96.3.123:54120 via WAN with router ON
Hence not possible via WAN
Observation
Via WAN when i try to connect....it gets disconnected very soon...meaning it seems as if it doesnt process the signal for a very long time....(just an observation... meaning as if some obstacle at the client end itself....but cant be sure, this is just an observation)
Query
In Client the windows firewall is on.....but the EXCEPTIONS tab doesnt have any port configured for remote client.... just wondering whether any configuration is needed (like port forwarding of windows firewall or router port forwarding) on the Client side. |
|
JamesLevinworth
@embarqhsd.net
| reply to JamesLevinworth
I'm back. Crazy morning....
In my haste this morning and thinking you had registry cheese going on from previous changes, I lost sight of the fact that I think (not sure, so please clarify) that you originally had a different machine name for each SERVER and CLIENT before you bridged their respective connections (Was that where pc1/2 came in?). If yes, then I'll elect to hold on 'fixing' that, unless something doesn't work (which I have seen bugs with this, but I won't digress more here at this point). Your hostnames (SERVER and CLIENT) exist appropriately as that is what their own names were for their respective connections prior to bridging (which would have been different at that point)... and seeing it now would be normal because they carried over.
I see you just posted an update as I was typing, so I'll go read that in the mean time... |
|
fms007
join:2009-05-24
| Both the hostnames (SERVER and CLIENT) before bridging and after bridging are/were the same.....meaning there is no change from the names they had before bridging....this i confirmed by checking the ipconfig.txt 4 files which i have (2 before bridging and 2 files after bridging)
SERVER
Computer Name:Server
Username:Server
CLIENT
Computer Name:Client
Username:Server |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
said by fms007  :Hi....i hope no damage from the fire.... Hey, thx. Drive crapped in the RAID (plus other bs). Nothing that can't be rebuilt.
said by fms007 :It worked perfect with the router off....both PCs also connect to the net independently. Checked in system properties... computer tab... Great. Very glad to hear things are working.
Quick question.. Your desire is to RDP to the server only, correct? And not client too? That was my impression, but I realize earlier
you tested going to CLIENT from SERVER which we didn't set up. If you do want that also, just say so.
BTW, Thanks for the very clear and concise results as you have been posting them.  |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
said by fms007 :Both the hostnames (SERVER and CLIENT) before bridging and after bridging are/were the same.....meaning there is no change from the names they had before bridging....this i confirmed by checking the ipconfig.txt 4 files which i have (2 before bridging and 2 files after bridging) SERVER Computer Name:Server Username:Server CLIENT Computer Name:Client Username:Server That I knew, but didn't you say something about having different machine names? what was pc1 and 2 about.? (Don't make me read back... lol) |
|
fms007
join:2009-05-24
2 edits | quote:
to SERVER (this i m asking for the computer named Client, PC2)...meaning if i change the name to SERVER will there be a conflict bcos there already is a computer named SERVER in the LAN (ie the first computer,PC1) and there cant be 2 computers with the same name....
I had written this in a previous post.....m sorry i only mentioned PC2 and PC1 to simplify (clarify)....there is no PC1 or PC2 ...yes only Server and Client.....the names are the same before bridging and after bridging....and i remember one of ur post about not using PC1 and PC2....so will not use it any further |
|
fms007
join:2009-05-24
| reply to JamesLevinworth
quote:
Drive crapped in the RAID
Really sorry to hear about the drive.
quote:
Quick question.. Your desire is to RDP to the server only, correct? And not client too?
I think for the time being let me try and get a connection to the server....if it works i can than try for the client.....right |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
Just a sanity check here...
(1.)Port forwarded registry settg....54120
You did this on SERVER (not CLIENT), correct?
(2.)Port forwarded router RDP-54120......54120
You pointed the port forward to SERVER (and server only), correct? Meaning, that's the only rule forwarding in 54120 through the router.
Does your router port forward option point to 192.168.1.2 or does it use the netbios name of SERVER (or both)?
I can't remember.
(3.)Disabled Outpost on server and client
Good.
(4.)Enabled Windows Firewall on server and client
Good.
(5.)Added exception to windows firewall on server for RDP-54120 and confirmed the rule had been added in exception list.
For SERVER only, correct?
(6.)Configured RDP client on Client (ie select Modem 28.8.... uncheck printers/clipboard....save as)
Good.
(if not on any, make it so...) |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
said by fms007 : quote:
to SERVER (this i m asking for the computer named Client, PC2)...meaning if i change the name to SERVER will there be a conflict bcos there already is a computer named SERVER in the LAN (ie the first computer,PC1) and there cant be 2 computers with the same name....
I had written this in a previous post.....m sorry i only mentioned PC2 and PC1 to simplify (clarify)....there is no PC1 or PC2 ...yes only Server and Client.....the names are the same before bridging and after bridging....and i remember one of ur post about not using PC1 and PC2....so will not use it any further Ah ok. I was pretty sure that was the case (using pc1/2 as symbolic names in your post), but then I thought you possibly did have different machine names (pc1/2) than you did/do for hosts names (server/client) existing at the same time. Just to clarify, Machine name and host name are 2 different things and can be different names. We're good. |
|
JamesLevinworth
@embarqhsd.net | To clarify, machine name = computer name in my post ... which again is a different thing than a host name.. but you have them the same in each machine, so we're good.. we're good... |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
said by fms007 : quote:
Drive crapped in the RAID
Really sorry to hear about the drive. At least data wasn't lost, just the drive... and my time to fix it... thx.
said by fms007 : quote:
Quick question.. Your desire is to RDP to the server only, correct? And not client too?
I think for the time being let me try and get a connection to the server....if it works i can than try for the client.....right Good plan. |
|
fms007
join:2009-05-24
| reply to JamesLevinworth
One final clarification please..
When i do ipconfig on SERVER i get
Hostname:SERVER
When i do ipconfig on CLIENT i get
Hostname:CLIENT
When i check right click computer properties...computer tab for SERVER i get
Computer description:SERVER
Full Computer Name:SERVER
Workgroup:HOME
When i check right click computer properties...computer tab for SERVER i get
Computer description:CLIENT
Full Computer Name:CLIENT
Workgroup:HOME
quote:
To clarify, machine name = computer name in my post ... which again is a different thing than a host name.. but you have them the same in each machine
Meaning on SERVER
Machine name=Computer name= hostname=SERVER
Meaning on CLIENT
Machine name=Computer name= hostname=CLIENT
This is what i should have...right |
|
fms007
join:2009-05-24
1 edit | reply to JamesLevinworth
(1.)Port forwarded registry settg....54120
Yes 54120 is showing for SERVER registry settings
Checked on CLIENT registry settings....shows default port 3389 which is fixed by windows.
(2.)Port forwarded router RDP-54120......54120
Yes RDP-54120...54120 is forwarded on router for ip 192.168.1.2.... the router port forward option point to 192.168.1.2 not to netbios name of SERVER
(3.)Disabled Outpost on server and client
Yes
(4.)Enabled Windows Firewall on server and client
Yes
(5.)Added exception to windows firewall on server for RDP-54120 and confirmed the rule had been added in exception list.
Yes
(6.)Configured RDP client on Client (ie select Modem 28.8.... uncheck printers/clipboard....save as)
Yes
I have double checked and attached a snapshot of the port forwarding of my router settings page for RDP |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
Yep... and Sorry, I was trying to clarify to avoid confusion futher.
You have (on server, for example):
Computer Name: SERVER (what I called machine name before)
Host Name: Server
Logon Name: Server
That's what you want. They just happen to all be 3 different things that are the same name (in your case). The first 2 are commonly the same (in part) and often enough that when they are not, it could mean registry cheese. We're good.
Can you go here and verify your WAN IP is the same that you are using in the RDP to test WAN, and also see if 54120 is open. Thx.
»www.canyouseeme.org/ |
|
fms007
join:2009-05-24
| Yes my WAN ip is the same that i m using in RDP and the port 54120 is also open
Message from CanYouSeeMe.org - Open Port Check Tool
"Success: I can see your service on 69.96.3.123 on port (54120)
Your ISP is not blocking port 54120" |
|
JamesLevinworth
@embarqhsd.net
| said by fms007 :Yes my WAN ip is the same that i m using in RDP and the port 54120 is also open Message from CanYouSeeMe.org - Open Port Check Tool "Success: I can see your service on 69.96.3.123 on port (54120)
Your ISP is not blocking port 54120" Ok, thx.
For all of these, we are testing WAN-RDP only, using the WAN IP address, no PORT, like this: 69.96.3.123
Disable windows firewall on client (only) TEST
Disable windows firewall on server(only) TEST
Disable both on both, TEST.
thx |
|
JamesLevinworth
@embarqhsd.net
| said by JamesLevinworth :
For all of these, we are testing WAN-RDP only, using the WAN IP address, no PORT, like this: 69.96.3.123
Disable windows firewall on client (only) TEST
Disable windows firewall on server(only) TEST
Disable both on both, TEST.
thx
Then also do with port, like this: 69.96.3.123:54120
AND then also try doing the LAN IP 192.168.1.2:54120 with the router on for all.
thx |
|
