All of a sudden, I can't get out to the web on the XP64 side of my machine. It's built on a Tyan 2895 with 2xOpterons and onboard gigabit. The nic is fine, as I can access my local intranet, and I can get out to the web on the XP32 side. When I try to get to the Intenet, I fnd that I can't get past my DHCP server. I've tried with two different DHCP servers, and it's not an issue with them. I can ping the DHCP servers, but nothing beyond them. I'm pretty sure that it's a setting on my box, and hope there's an XP64 network expert out there who can lend some advice. Thanks!

Follow the same troubleshooting steps you would on 32 bit. IP v4 is IP v4 no matter what OS you are using.

Thanks. I did that. All the basic settings are the same, and I run the same applications on each side. I'm thinking perhaps a policy setting.

Is the problem with pinging out to the 'net, or is it just an IE32 or IE64 problem?

Can you ping 127.0.0.1?

Can you ping your default gateway?

Can you resolve names?

Can you tracert to well known sites?

Jim

The problem exists with IE32 and IE64.

>Can you ping 127.0.0.1?
Yes
>Can you ping your default gateway?
Yes
>Can you resolve names?
No
>Can you tracert to well known sites?
No

My DHCP server is my default gateway, but the Default Gateway did not show up in ipconfig until I entered it manually, although that did not get me out to the Net. Thanks very much!

What happens if you ping 141.149.134.194? And tracert to the same?

try setting your dns server to 4.2.2.2?

First, this should be posted on the Networks, Internet & Security forum.

The problem is on your DHCP scope options. You need to add the right DNS Server IP and the right Gateway, so, when the DHCP provides you with a IP, it also gives you all the other "stuff" you need. (DNS, Gateway)

Thanks for the suggestion. Sorry if I posted to the wrong forum, but since this issue is unique (in my case) to XP64, I thought I'd post here.

I manually set up the IP, subnet, default gateway, and prim/alt DNS servers. Still can't get out. The same, manual setup can get out on the 32 side. If things worked as they should, everything would be supplied automatically, as on the 32-bit side. I was able to get out a few weeks ago in 64, using the auto IP/DNS, so something's gone wrong in the meantime.

Things dont get supplied automatacly.

If you have a DHCP Server, you need to configure the scope by wich he will be assigning IP addresses. Configuring a DHCP Server Scope options is not saying it will give IPs from 10.0.0.x - 10.0.0.y.

You can, and should, define on the Scope Options, the DNS server, NetBIOS, Gateway, etc etc. You have allot of options.

If you cant "get out", thats a ottaly different issue. Try ping something outside your network/subnet (using IP and FQDN). If IP works and FQDN doesnt, you have a DNS problem.

You need to make a drawing on paint or something to help us understand your network.

Did you stop/disable the "DNS Client" service?

Thanks again. Normally, I could get out to the NET by simply chosing to obtain IP and DNS automatically. I still can't get out even if I "hard code" the IP/Subnet/Gateway/DNS. My gateway/DHCP is 192.168.0.1. My machine is 192.168.0.3. DNS service is enabled. Below is a partial printout:

Active Routes:
Network Destination.........Netmask.........Gateway...........Interface
0.0.0.0...........................0.0.0.0............192.168.0.1....192.168.0.1
127.0.0.0........................255.0.0.0.........127.0.0.1.........127.0.0.1
192.168.0.0....................255.255.255.0...192.168.0.1......192.168.0.1
192.168.0.0....................255.255.255.0...192.168.0.3......192.168.0.3
192.168.0.1...................255.255.255.255..127.0.0.1........127.0.0.1
192.168.0.3..................255.255.255.255...127.0.0.1.........127.0.0.1

I believe that the first line reveals an error, being that the Interface should be my IP address of 192.168.0.3, and not 192.168.0.1. I can ping my DHCP, but I cannot ping an outside IP or FQDN. Regarding the network, I go directly from the NIC to a switch, which goes to the DSL router, and that setup works on the 32-bit side of the same machine/same NIC. I'd be happy to supply any further details. Thanks!

Is this machine multi-homed?
If that is output from "route print" on the XP x64 machine then it seems to imply that it has 2 interfaces (or at least 2 bound IP addresses) on the 192.168.0.0/24 network...

I agree with Gouki that we need either a diagram of your network to understand the layout, and ideally the complete output from:
ipconfig /all
route print

Thanks. I'm not sure what you mean by "multi-homed." I attached files with outputs from the commands. NETWORK 2 is the one with the issue, but the issue will exist with either NIC. Perhaps there's a conflict with VMware.

Well, I just unistalled VMware, and I can get out. You might have seen this in the files I attached with my last post, but, after the uninstall, this is the ipconfig frm the particular NIC:
Connection-specific DNS Suffix . : domain.actdsltmp
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::2e0:81ff:fe54:c788%4
Default Gateway . . . . . . . . . : 192.168.0.1

What's the second IP address that's two-byte hex strngs? It's not my or the gateway's IP. Thanks!

You don't know what multi-homed means, but you have installed VMWare on this machine and the host is trying to obtain DHCP settings from one of its guests?

Okay, uninstall IPv6 as you will not need it.
You can't route anywhere as you don't have a default gateway on the network adapter, and did you join the host to a domain running on a server in a guest OS or something? (DNS suffix is "domain.actdsltmp")


Your VMWare (possibly NAT?) adapter appears to have a conflicting subnet with your physical network.
192.168.0.1 must be your router, connected to the LAN that "NETWORK 2" is connect to, but when VMWare is installed it is screwing up the configuration by putting the IP of your router on the virtual interface.

Multi-homed means the machine has multiple network interfaces (physical or virtual).
Your machine is multi-homed with 2 physical network adapters (192.168.0.0/24 and 10.10.10.0/24) and with 2 virtual network adapters provided by VMWare (192.168.0.0/24 and 192.168.40.1).

The strange-looking IP addresses are IPv6 which you will not need.

A gateway is the device which network traffic is sent to when the destination is not on your local networks.
Having no default gateway means you can't route.
Having more than one gateway can cause routing problems or delays as the computer will just the use first it "sees" even if it isn't right (unless you set up static routes).

Leave VMWare out of the equation until you understand more about networks & IP routing, then reconfigure "VMware Virtual Ethernet Adapter for VMnet8" so it doesn't try to use the same subnet as your physical network adapter.

Thanks very much for your patience and help. "Multi-homed" is not a term that I've heard for multiple adapters, despite my advanced years and at least modest talent. Sorry. I will admit to being foolish in not observing that VMnet8 had already grabbed the default gateway as its IP address. I skipped right by that, as there were no VMs running, and I didn't stop to think that the virtual adapter would have grabbed the gateway's address as its IP. For one, it shouldn't have the same IP for the adapter and gateway. As I mentioned, this came about suddenly, after VMware has been in substantial use.

After reinstalling VMware, all is well, as its adapters assumed IPs elsewhere in the 192.168 range. Perhaps what happened is that, when I ran a VM with NAT or changed the IP within the VM to use DHCP, it assumed my gateway's IP as its own, and I neglected to reset the address. When I run a VM with networking, it's generally bridged to the host's physical adapter. As you observed, TCP/IP is not my strong point, but I do know enough to (usually) get by. For the times when I don't, I'm grateful to folks like you who can point out the obvious. Thanks again.