Lets try and resolve this one more time ?
#1
Hi all,
A few months back, I posted looking for help with my home network and sharing a printer on a XP with a ME box. Never did get to the bottom of it.
Heres the background
XP box, connected to cable router (LinksysBEFSHR41)
ME box, connected to cable router
Cable router connected to cable modem (Telewest/Blueyonder)
Internet access/email access works fine on both boxes.
XP IP address 192.168.1.101
ME IP address 192.168.1.100
Cable Router 192.168.1.1
I've done all the "enable printer for sharing" stuff. My main problem seems to be connectivity.
XP can ping ME
XP can ping Cable Router
XP cant access Cable Router config page (http://192.168.1.1) but remember, it can ping this address
ME cant ping XP
ME can ping cable router
ME can access cable router config page
I am WELL confused
Any help appreciated.
David.
A few months back, I posted looking for help with my home network and sharing a printer on a XP with a ME box. Never did get to the bottom of it.
Heres the background
XP box, connected to cable router (LinksysBEFSHR41)
ME box, connected to cable router
Cable router connected to cable modem (Telewest/Blueyonder)
Internet access/email access works fine on both boxes.
XP IP address 192.168.1.101
ME IP address 192.168.1.100
Cable Router 192.168.1.1
I've done all the "enable printer for sharing" stuff. My main problem seems to be connectivity.
XP can ping ME
XP can ping Cable Router
XP cant access Cable Router config page (http://192.168.1.1) but remember, it can ping this address
ME cant ping XP
ME can ping cable router
ME can access cable router config page
I am WELL confused
Any help appreciated.
David.
#2
Have you checked the firewall rules in the cable router ? Also take a look at the firewall rules in XP as it sounds like these could be causing problems also.
e.g
Go to your network connection and right-click to Properties. Then go to Advanced which brings up the native firewall. Click Settings and then ICMP. Click on "Allow incoming echo request." You will then be pingable.
[Edited by michael_clarkson - 5/16/2003 11:58:57 AM]
e.g
Go to your network connection and right-click to Properties. Then go to Advanced which brings up the native firewall. Click Settings and then ICMP. Click on "Allow incoming echo request." You will then be pingable.
[Edited by michael_clarkson - 5/16/2003 11:58:57 AM]
#3
Scooby Regular
Join Date: Aug 2002
Location: not forgetting 20,000 posts from last time ;)
Posts: 5,806
Likes: 0
Received 0 Likes
on
0 Posts
Check that both machines have same subnet mask set (255.255.255.0)
Have you created a username on the XP box which exactly matches that on the ME box?
Have you created a username on the XP box which exactly matches that on the ME box?
#6
Scooby Regular
Join Date: Aug 2002
Location: not forgetting 20,000 posts from last time ;)
Posts: 5,806
Likes: 0
Received 0 Likes
on
0 Posts
I guess you are using static IPs.
Has the router got DHCP enabled? If so, are your static IPs clashing with the DHCP range?
Have you tried using dynamic IPs (i.e. the PCs getting IP address automatically from router)?
Do all other settings match (e.g. gateway, DNS etc)
Has the router got DHCP enabled? If so, are your static IPs clashing with the DHCP range?
Have you tried using dynamic IPs (i.e. the PCs getting IP address automatically from router)?
Do all other settings match (e.g. gateway, DNS etc)
Trending Topics
#10
Scooby Regular
Join Date: Aug 2002
Location: not forgetting 20,000 posts from last time ;)
Posts: 5,806
Likes: 0
Received 0 Likes
on
0 Posts
Not sure about dynamic routing - would leave it be for the time being.
Check TCP/IP properties on thePCs - see if set for static or automatic IPs.
Check TCP/IP properties on thePCs - see if set for static or automatic IPs.
#11
you may need to check that the defulat gateway is set. you are able to ping which shows a physical route, but your PC may not know how to route the ping to the destinations if it cannot find a gateway - this should be the IP address of your router.
H:\>ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : whatever
IP Address. . . . . . . . . . . . : 10.1.99.236
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.99.254
hope this helps.
andy b.
[Edited by micaAB - 5/16/2003 12:34:34 PM]
H:\>ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : whatever
IP Address. . . . . . . . . . . . : 10.1.99.236
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.99.254
hope this helps.
andy b.
[Edited by micaAB - 5/16/2003 12:34:34 PM]
#12
C:\>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : MSHOME
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : MSHOME
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
#13
I have now manage to get the XP box to gain access to the router config page by opening explorer window, tools, internet options, connection, LAN settings, then unchecking automatically detect settings and proxy servers.
Getting there slowly.
Getting there slowly.
#16
may be a routing table thing then - you're getting a ping into the router, but trying to ping to the other PC is the problem.
from the ME try:
route print
and
tracert 192.168.1.101
if you can access the router with a telnet session you can do a "route print" there too and then put it up on here (now to be honest i probably won't be able to interpret this information correctly - not smart enough, but there's gotta be some smart guy reading this who can tell you if the routing entries are correct). this is the basics of ip diagnosis, i'm not leading you up a garden path honest:
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.1.10.254 10.1.10.236 1
10.1.10.0 255.255.255.0 10.1.10.236 10.1.10.236 1
10.1.10.236 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.1.10.236 10.1.10.236 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.1.10.236 10.1.10.236 1
255.255.255.255 255.255.255.255 10.1.10.236 10.1.10.236 1
Default Gateway: 10.1.10.254
================================================== =========================
Persistent Routes:
None
from the ME try:
route print
and
tracert 192.168.1.101
if you can access the router with a telnet session you can do a "route print" there too and then put it up on here (now to be honest i probably won't be able to interpret this information correctly - not smart enough, but there's gotta be some smart guy reading this who can tell you if the routing entries are correct). this is the basics of ip diagnosis, i'm not leading you up a garden path honest:
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.1.10.254 10.1.10.236 1
10.1.10.0 255.255.255.0 10.1.10.236 10.1.10.236 1
10.1.10.236 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.1.10.236 10.1.10.236 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.1.10.236 10.1.10.236 1
255.255.255.255 255.255.255.255 10.1.10.236 10.1.10.236 1
Default Gateway: 10.1.10.254
================================================== =========================
Persistent Routes:
None
#22
C:\>route print
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 20 ed 41 b6 e3 ...... Realtek RTL8139/810x Family Fast Ethernet NIC -
Packet Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 20
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 20
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100 1
Default Gateway: 192.168.1.1
================================================== =========================
Persistent Routes:
None
Well, I've no idea if this is right or wrong
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 20 ed 41 b6 e3 ...... Realtek RTL8139/810x Family Fast Ethernet NIC -
Packet Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 20
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 20
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100 1
Default Gateway: 192.168.1.1
================================================== =========================
Persistent Routes:
None
Well, I've no idea if this is right or wrong
#27
Scooby Regular
Join Date: Aug 2002
Location: not forgetting 20,000 posts from last time ;)
Posts: 5,806
Likes: 0
Received 0 Likes
on
0 Posts
David,
Back to what I suggested earlier, check to ensure the PCs are not set for static IP's as these will possibly clash with the routers DHCP allocation.
I also suggest you run the XP Network setup Wizard, then create a network setup disk and run this on the ME machine.
HTH
Back to what I suggested earlier, check to ensure the PCs are not set for static IP's as these will possibly clash with the routers DHCP allocation.
I also suggest you run the XP Network setup Wizard, then create a network setup disk and run this on the ME machine.
HTH
#28
David,
It still sounds like you have the WinXP FW switched on, and that would be one reason why you can't ping the box.
Go to your network connection and right-click to Properties. Then go to Advanced which brings up the native firewall. Click Settings and then ICMP. Click on "Allow incoming echo request." You will then be pingable.
It still sounds like you have the WinXP FW switched on, and that would be one reason why you can't ping the box.
Go to your network connection and right-click to Properties. Then go to Advanced which brings up the native firewall. Click Settings and then ICMP. Click on "Allow incoming echo request." You will then be pingable.
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
28
28 December 2015 11:07 PM